Blaster Dev GitOps Via Flux Runbook
Runbook on how the blaster game moves from local development to Kubernetes dev and prod using GitLab, Kaniko, FluxCD and dynamic images.
Runbook on how the blaster game moves from local development to Kubernetes dev and prod using GitLab, Kaniko, FluxCD and dynamic images.
Structure and contents of the Blaster app Kubernetes manifests under k8s/dev and k8s/prod, including secrets, database, deployment, ingress and SOPS encryption.
How the Blaster Dockerfile and GitLab CI pipeline work together to build, tag and push images for FluxCD GitOps.
How the Blaster app and infra repos are structured, how branches map to environments, and how merge requests control promotion from dev to prod.
How FluxCD GitRepository and Kustomization resources are configured for the Blaster game, including bootstrap, SOPS decryption and the blaster-dev environment.
How Flux image automation discovers Blaster images in the GitLab registry, picks the latest dev tag, and updates the k8s/dev Deployment manifest in Git.
How SOPS and age are used to encrypt secrets for the Blaster app and Flux GitOps configuration across app and infra repositories.
End to end verification and troubleshooting guide for the Blaster GitOps stack, covering Git, CI, SOPS, Flux, image automation and Kubernetes health.
Runbook on how the blaster game moves from Kubernetes dev to prod using GitLab, Kaniko, FluxCD and dynamic images.