Skip to main content
And just like that, we’ve arrived at the final section. In this lesson we’ll combine everything we’ve learned into a minimal, production-ready GitOps template that ties together Glasskube, Argo CD, and the package manifests required to bootstrap a Kubernetes cluster. We’ll start with a concise GitOps refresher to ground the workflow and explain why we choose this approach for cluster bootstrapping and ongoing operations. This section focuses on:
  • A short GitOps refresher and the benefits it provides teams
  • The end-to-end workflow that the Glasskube + Argo CD template will implement
  • A minimal repository layout and example manifests to get a cluster ready in seconds
  • Practical considerations for safely managing configuration and secrets during bootstrap
GitOps enables declarative, Git-centered operations for Kubernetes. By storing cluster state in Git and using Argo CD to continuously reconcile the cluster, you get auditable changes, safer rollbacks, and repeatable cluster bootstraps.

​
Why GitOps for cluster bootstrap

GitOps is particularly well suited for cluster bootstrap and platform configuration because it makes the desired state explicit, versioned, and reviewable. Key benefits include:
  • Improved collaboration via Git-based code review and approvals
  • Safer, auditable configuration changes and clear rollback paths
  • Reliable, automated deployments with continuous reconciliation
  • Faster onboarding and reproducible environments

​
What you’ll build

By the end of this lesson you will have a working Kubernetes cluster configured using a minimal Glasskube GitOps template. The template is intentionally minimal so you can:
  • Quickly provision a cluster with common platform packages
  • See how Argo CD reconciles the repository to the cluster
  • Extend the template for your environment and policies

​
GitOps workflow (high level)

  1. Define the desired cluster state in a Git repository (infrastructure, packages, configs).
  2. Argo CD watches the Git repo and reconciles the cluster to match the declared state.
  3. Changes are made via Git (pull requests), reviewed, and merged — Argo CD applies them automatically.
  4. Continuous monitoring ensures drift is corrected and the repo remains the single source of truth.

​
Example repository layout

Below is a minimal repo layout you can use as a starting point for a Glasskube + Argo CD GitOps template:

​
Minimal Argo CD Application example

This example shows an Argo CD Application that targets the clusters/production path in the repository. Customize destination.server and destination.namespace for your cluster.
Avoid committing plaintext secrets to Git. Use sealed-secrets, external secret stores (e.g., AWS Secrets Manager, HashiCorp Vault), or GitOps-compatible secret management to keep sensitive data safe.

​
Practical tips for a minimal Glasskube template

  • Start with a small set of packages that are essential for cluster operation (RBAC, ingress, monitoring).
  • Keep overlays simple and use Kustomize or Helm charts as needed.
  • Configure Argo CD with prune and selfHeal to ensure the cluster converges to Git state.
  • Use branch protection and PR reviews to enforce change control.
Throughout the lesson you’ll practice these concepts and configurations. By following this template you’ll be able to provision and maintain a cluster that is auditable, reproducible, and ready for rapid iteration.

Watch Video