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.
How the Blaster app and infra repos are structured, how branches map to environments, and how merge requests control promotion from dev to prod.
Workload placement controls and examples.
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.
No inbound firewall ports open.
Replace the virtual worker with a physical node to make the development cluster hybrid. This adds realistic CPU, memory, storage, and network performance while keeping the control plane simple and virtualised.
Install and join process for the physical node.
Validation commands and expected outputs.