Declare environment differences
Use Helm and umbrella-chart patterns to represent environment configuration consistently.
Back to projectsOngoing
Infrastructure / Kubernetes / GitOps
Kubernetes and GitOps Infrastructure
Designed and operated GitOps-based Kubernetes workflows using Argo CD, Helm, and deployment automation patterns for production environments.
Delivery workflow
Repeatable Kubernetes delivery
A conceptual GitOps delivery path connecting pipeline automation, desired configuration and controlled Kubernetes rollout.
Automate delivery
Connect CI/CD to repeatable deployment workflows.
- GitLab CI
- Docker
Declare the desired state
Helm-based environment configuration reconciled through GitOps.
- Helm
- Argo CD
Roll out & route
Kubernetes deployment governance and ingress/gateway patterns.
- Kubernetes
- Argo Rollouts
- Gateway API
The challenge
Production deployments need predictable governance, repeatable configuration, and a delivery model that engineers can operate safely.
The approach
Built GitOps workflows with Argo CD, Helm charts, ingress and gateway patterns, and deployment automation that fits production operations.
My role
Worked across Kubernetes operations, Helm chart design, Argo CD usage, and production deployment workflows.
Engineering decisions
Keep rollout governance explicit
Combine GitOps with rollout and gateway patterns that fit production operations.
Scope & delivery
- GitOps workflows with Argo CD and Helm.
- Umbrella chart and environment configuration patterns.
- Ingress, Gateway API, Argo Rollouts, and deployment governance concepts.
- CI/CD integration for repeatable Kubernetes delivery.