DevOps • Platform Engineering • Cloud Infrastructure

Build faster. Ship safer.

AWS, EKS, Kubernetes, Terraform, GitHub Actions, and self-hosted GitLab. Focused on delivery automation, platform consistency, safer infrastructure changes, and systems that stay maintainable after the first rollout.

  • AWS / EKS
  • Terraform
  • GitHub Actions
  • Self-hosted GitLab
  • Platform Engineering
About

David Buňka

DevOps engineer based in Pohořelice, South Moravia, Czech Republic. Daily work centers on AWS, EKS, Kubernetes, Terraform, GitHub Actions, and self-hosted GitLab. Most of the engineering focus is on platform reliability, delivery automation, cleaner infrastructure boundaries, and repeatable operating patterns for teams shipping through CI/CD every day.

Career profile

  • DevOps and platform engineering in cloud-native environments
  • AWS and Kubernetes infrastructure with EKS at the center
  • Terraform-heavy infrastructure design, imports, refactoring, and state strategy
  • Daily work with GitHub Actions and practical experience with self-hosted GitLab
Focus

Core areas

Technical areas that define the current DevOps and platform engineering profile.

Cloud platforms on AWS

AWS environments with clear boundaries across compute, IAM, networking, access, and deployment paths.

  • AWS platform foundations
  • EKS cluster architecture and operations
  • IAM, OIDC, and IRSA patterns

CI/CD engineering

Delivery workflows optimized for repeatability, reviewability, and operational safety.

  • GitHub Actions reusable workflows
  • self-hosted and ARC runner strategy
  • GitLab CI pipelines for self-hosted environments

Kubernetes operations

Day-2 engineering for platforms that need predictable scaling, cleaner standards, and fewer production surprises.

  • workload conventions and cluster hygiene
  • Karpenter node strategy and scaling
  • deployment reliability and platform guardrails

Infrastructure as code

Terraform codebases designed to stay understandable across teams, repositories, and environments.

  • module design and repository structure
  • state separation, imports, and migrations
  • drift control and review-friendly changes
Toolset

Tools and platforms

Core stack used across cloud platforms, delivery pipelines, and infrastructure automation.

  • AWS
  • EKS
  • Kubernetes
  • Karpenter
  • Terraform
  • GitHub Actions
  • Actions Runner Controller
  • Self-hosted GitLab
  • GitLab CI
  • Docker
  • Linux
  • Bash
  • Python
  • OIDC / IRSA
  • Observability

Engineering approach

  • prefer reusable building blocks over one-off fixes
  • optimize for maintainability, not just first deployment
  • reduce plan noise and pipeline complexity
  • keep delivery fast without losing operational control
Work

Representative work areas

Areas that align with the current toolset and day-to-day engineering focus.

GitHub organization and delivery automation

Reusable workflows, repository standards, secrets handling, and self-hosted runner patterns for teams using GitHub Actions as a daily delivery platform.

AWS EKS platform engineering

Cluster operations, IAM integration, node lifecycle strategy, workload scheduling, and conventions that keep Kubernetes platforms manageable over time.

Terraform refactoring and state strategy

Splitting large codebases into clearer boundaries, improving import workflows, and reducing plan noise across teams and environments.

Mixed GitLab and GitHub delivery environments

Working across self-hosted GitLab and GitHub-based delivery flows where consistency, access control, and release safety matter.

Profiles

Public profiles

Public contact points and profiles related to David Buňka.

Primary toolset

  • AWS, EKS, Kubernetes, and Karpenter
  • Terraform modules, imports, and state boundaries
  • GitHub Actions, reusable workflows, and runner strategy
  • Self-hosted GitLab and GitLab CI delivery flows