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.
High-level overview of how the Blaster demo game is used as a worked example of moving from local development to Kubernetes dev and prod using GitLab, Kaniko and FluxCD.
This runbook provides end-to-end instructions on how to deploy and manage Cloudflare and the Cloudflare CA issuer onto the cluster using GitOps automation via Flux.
High-level architecture for the dual-IdP ZITADEL setup, showing how public and internal identity, GitOps repos, databases, trust and apps fit together, with links to the detailed identity runbooks.
Runbook on how the blaster game moves from Kubernetes dev to prod using GitLab, Kaniko, FluxCD and dynamic images.
Add the WordPress app repo into `flux-config` by defining the namespace, GitRepository, and Kustomization objects, then reconcile and verify.
High-level overview of the WordPress-on-Kubernetes GitOps workflow (repo layout, Flux configuration, restore and ops toolkit).
Archived on high.
Application repository Kubernetes manifests under `k8s/prod`, including SOPS policy, Secrets, MariaDB, WordPress, Ingress, cron, Redis, NetworkPolicies, and Kustomize configuration.
Restore workflow (DB then wp-content), wpcli-shell procedures, manual and Velero backups, post-migration steps, and security hardening notes.
Prerequisites, local tooling verification, Cloudflare portal hardening, and initial GitLab app repository setup for a Flux-managed WordPress deployment.