43 docs tagged with "gitops"

Components, data flow, and external integrations for the Cal.com scheduling stack.

Components, email flow, and attack scenarios protected by the email relay.

Components, data flow, and resource requirements for the observability stack.

How to run Blaster in production. Self-hosted, Vercel, and Kubernetes with GitOps.

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.

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.

How the Blaster app and infra repos are structured, how branches map to environments, and how merge requests control promotion from dev to prod.

Repo preparation before k8s deployment.

End-to-end Clerk setup for the Blaster game, from dev to production, including domains, Google OAuth, CI variables and Kubernetes wiring.

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.

Kubernetes deployment with Flux GitOps, database setup, and CronJob configuration.

Kubernetes deployment with Flux GitOps, database backup infrastructure, and CI/CD pipeline for the school platform.

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.

Shared SMTP relay infrastructure with MX domain validation, email logging, and Microsoft 365 Graph API delivery.

Flux configuration with dependency control and deployment commands for the Cal.com scheduling stack.

GitOps deployment with image automation for the email relay.

Flux configuration with dependency control and deployment commands for the observability stack.

GitOps overview.

Configure Google OAuth for Clerk in the Blaster production deployment, from Google Cloud and Clerk setup through to testing and common error patterns.

High level overview of the dual ZITADEL identity providers, why this pattern exists, and how to navigate the identity runbooks.

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.

Protect Kubernetes Dashboard with OAuth2 Proxy using the internal ZITADEL instance, with secrets stored in Git via SOPS and deployed by FluxCD.

App repo structure and key manifest configurations for the Cal.com scheduling stack.

Repository structure, mx-validator code, and Kubernetes manifests for the email relay.

App repo structure and key manifest configurations for the observability stack.

Self-host a meeting scheduling system using Cal.com with GitOps, saving hundreds in SaaS fees.

Deploy a GitOps-managed observability stack with Prometheus, Loki, Grafana Alloy, and Uptime Kuma for proactive alerting on application-level issues.

OAuth setup, email via Graph API, security hardening, first login, and troubleshooting for the Cal.com scheduling stack.

Azure App Registration, smtp2graph configuration, Prometheus metrics, and troubleshooting.

Post-deployment setup, testing alerts, and troubleshooting for the observability stack.

High level overview of the Blaster production deployment, with pointers to detailed runbooks for Kubernetes manifests, Flux GitOps, Cloudflare and security hardening.

Runbook for configuring FluxCD to deploy Blaster prod from the your-org/blaster repo with SOPS decryption and automated image updates.

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.

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.