tag: fluxcd
- Wildcard TLS with ACME and cert-manager: Automating Let's Encrypt via Yandex Cloud DNS How ACME and DNS-01 work, why wildcard certs require it, and how to automate Let's Encrypt in Kubernetes with cert-manager and the Yandex Cloud DNS webhook in a FluxCD GitOps setup.
- Debugging Flux reconciliation: a field guide Where to look when Flux doesn't reconcile: get all, describe, force reconcile, suspend/resume, common error patterns for Kustomization and HelmRelease.
- Adding a new environment to a FluxCD hub-and-spoke cluster Full checklist: provision cluster, seal kubeconfig, create Kustomize overlays, patches, routes, and register in the Flux root kustomization.
- Flux Image Update Automation: auto-bump image tags in git ImageRepository scans the registry, ImagePolicy selects the right tag (semver, regex), ImageUpdateAutomation commits the updated tag back to git via marker annotations.
- GitLab CI for an infra repo: lint, validate, and flux reconcile Pipeline stages for a Kubernetes infra repository: yamllint, kubectl kustomize per environment, flux reconcile on merge, Telegram/Mattermost notifications.
- Flux Notification Controller: commit status, Telegram, Mattermost Provider and Alert CRDs: GitLab commit status on every reconcile, generic webhook to abot for Telegram fan-out, per-namespace Alert objects for environment-scoped noise.
- Bootstrapping k3s clusters with Ansible and Flux Ansible handles OS prep, k3s install, and Cilium setup. Flux bootstrap via ansible-playbook. Spoke kubeconfigs sealed and committed.
- FluxCD hub-and-spoke: one cluster to manage them all FluxCD v2 hub-and-spoke: hub cluster runs Flux controllers, spoke clusters are managed via spec.kubeConfig in HelmRelease and Kustomization. KubeConfig secret setup, dependsOn across clusters.
- Kustomize base/custom/patch: DRY Helm values across environments Three-tier Kustomize layout for six clusters: shared base, optional custom components, env-specific delta patches. The directory-only rule and kubeConfig JSON patch.
- FluxCD hub-and-spoke: managing multiple Kubernetes clusters from one git repo Flux runs on one hub cluster and deploys to five spokes via kubeConfig secrets. The four Kustomization objects per environment, dependsOn ordering, and daily operations.
No posts match the selected filters.