Git-centered workflow orchestrating Terraform and FluxCD
Back to Portfolio
Infrastructure & Delivery as Code

GitOps Implementation

End-to-end GitOps setup that turns a Git repository into the single source of truth for both cloud infrastructure and Kubernetes workloads—secure by design, automated, and auditable.

The Challenge

Centralize control of infrastructure and application delivery with security and auditability—without scattering configs, secrets, or manual steps.

One place to control everything

Unify infra and app delivery so changes are reviewed, versioned, and reproduced from a single repo.

Heterogeneous infrastructure

Manage cloud resources, DNS, networking, databases, and Kubernetes clusters as code.

Secret management

Keep credentials out of repos while enabling safe automation for Terraform and Kubernetes.

Automated, gated deploys

Promote from staging to production with policies, image pinning, and reliable rollbacks.

Our GitOps Approach

Two cohesive layers: Terraform for cloud resources and FluxCD for Kubernetes delivery—both driven from Git.

1

Repo as Source of Truth

All desired state—infra modules, K8s manifests, environments, policies—lives in Git with peer-reviewed pull requests.

2

Terraform: Infrastructure as Code

Provision Google Cloud resources, networking, managed SQL/databases, and DNS (Cloudflare or cloud DNS) via reusable modules.

3

Secure Secrets via 1Password

Integrate 1Password with Terraform and Kubernetes so no secrets are stored in the repo; workloads reference injected secrets at runtime.

4

FluxCD: Kubernetes GitOps

Flux controllers reconcile cluster state from Git, applying manifests (Helm or Kustomize) until the live state matches the desired state.

5

Image Automation & Policies

Define image repositories and policies so Flux only upgrades to images that meet version rules; successful builds roll out automatically.

6

Staging → Production Promotion

Isolate environments with separate folders/branches; promote via PRs for auditable, policy-driven rollouts and easy rollbacks.

7

Automated Terraform Pipeline

GitHub workflow plans on PRs and applies on merge, making infra changes transparent and controlled.

8

Observability & Ops

Cluster is instrumented end-to-end; monitoring and metrics surface drift, performance, and deployment health.

Outcomes & Advantages

Speed, safety, and shared visibility for both platform and app teams.

Total visibility

Every change is tracked in Git—who changed what, when, and why—across infra and apps.

Security by default

Secrets never touch the repo; least-privilege automation and policy-gated promotions reduce risk.

Reliable rollbacks

Revert infrastructure and deployments to any known-good state quickly.

Faster delivery

Automated plans, reconciliations, and image updates shorten lead time from commit to production.

Extensible & modular

Add new services, clusters, or providers by composing Terraform modules and GitOps folders.

Tech Stack

Cloud-native tooling for predictable infrastructure and continuous delivery.

Infrastructure as Code

  • Terraform: Modules for GCP resources, networking, managed databases, and DNS.
  • GitHub Actions: CI workflows to plan on PR and apply on merge.
  • Cloud DNS / Cloudflare DNS: Authoritative DNS zones managed as code.

Kubernetes Delivery

  • FluxCD: GitOps controllers, image automation, and policy-based updates.
  • Kustomize / Helm: Templating and overlays for environment-specific manifests.
  • Kubernetes: Runtime for workloads, reconciled continuously from Git.
  • Docker: Container format for application builds.
  • Traefik: Ingress and edge proxy for routing and TLS.

Security & Secrets

  • 1Password: Secret injection for Terraform and Kubernetes; nothing stored in Git.

Observability

  • Prometheus: Metrics collection for clusters and workloads.
  • Grafana: Dashboards and alerting for performance and health.

Ready to Implement GitOps for Your Organization?

Transform your deployment process with GitOps practices that improve reliability, security, and team productivity.