How eddycharly/kind-playground works
Project type and purpose
• This is an infrastructure-as-code/GitOps “playground” for spinning up a local Kubernetes cluster using Kind, Cilium CNI, MetalLB, ingress-nginx, dnsmasq, Keycloak SSO and an ArgoCD-driven GitOps pipeline. It combines shell scripts, Helm charts, Terraform, raw manifests and ArgoCD Application definitions to bootstrap, configure and operate your entire stack locally.
File structure
• Top-level scripts:
• cluster.sh: bootstraps Kind cluster + Cilium CNI, MetalLB, ingress, dnsmasq, container-registry proxies
• keycloak.sh: deploys Keycloak + configures it via Terraform for OIDC
• argocd.sh: deploys ArgoCD configured for Keycloak OIDC
• argocd-applications.sh/gitops.sh: batch-apply ArgoCD Application manifests
• wipe.sh: teardown logic
• Directories:
• argocd/: ArgoCD Application manifests (one YAML per app)
• helm/gitops/: a Helm chart packaging all core components (argocd, cert-manager, cilium, ingress-nginx, etc.) plus network policy templates
• manifests/: raw Kubernetes manifests (Mattermost ingress)
• terraform/keycloak/: Terraform code to configure Keycloak realm, clients, users for SSO
• Configuration files:
• Helm Chart.yaml, values.yaml, .helmignore
• Terraform .tf files
• .gitignore
Extract additional insights from README
• Workflow:
• Run cluster.sh → Kind cluster + core networking + identity proxy
• Run keycloak.sh → Keycloak installed in the cluster + Terraform-backed realm/client setup
• Run argocd.sh → ArgoCD installed, pointing at Keycloak OIDC
• Use ArgoCD CLI or UI to sync Applications declared in argocd/
• Emphasis on local “play” environment, SSO integration, GitOps control plane
a. Main components
• Developer workstation (scripts + Git repository)
• Kind Kubernetes cluster (control plane & worker nodes)
• Core cluster services: Cilium CNI, MetalLB, ingress-nginx, dnsmasq, registry proxies
• Identity layer: Keycloak (deployed inside the cluster + external access)
• GitOps control plane: ArgoCD
• Application layer: cluster apps managed by ArgoCD (Cert-Manager, Gitea, Prometheus, etc.)
• Terraform module (external process) configuring Keycloak realm/client
b. Relationships & interactions
• Dev runs shell scripts → calls kind + kubectl + helm to install core services
• Terraform CLI → interacts with Keycloak’s HTTP API inside cluster
• ArgoCD watches this Git repo → reads argocd/*.yaml → deploys/monitors target apps
• Kubernetes API server delegates auth to Keycloak OIDC
• External traffic flows through MetalLB → ingress-nginx → specific services
• Cilium enforces network policies (from helm/gitops/templates/network-policies)
c. Architectural patterns & principles
• GitOps: declarative desired state in Git, ArgoCD as reconciliation engine
• Infrastructure as code: scripts + Helm + Terraform
• Modular: each system component (network, identity, GitOps, apps) isolated in its own manifest/chart/module
• Zero trust networking via Cilium + network-policy templates
d. Key technologies/frameworks
• Kind (Kubernetes-in-Docker)
• Kubernetes API, kubectl
• Cilium CNI, MetalLB, ingress-nginx, dnsmasq
• Helm chart for core services
• Terraform for Keycloak realm configuration
• Keycloak (OIDC provider)
• ArgoCD (GitOps controller)
• Various cluster applications (Cert-Manager, Gitea, Prometheus, Mattermost, etc.)