weblogtag
gitops
12 posts with this tag, newest first.
Tags, archive, series1 active
Tags
Archive
More
Posts 12
-
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.
-
Terraform Operator: running Terraform apply from inside Kubernetes
GalleyBytes terraform-operator runs Terraform as a CRD workload. State on a PVC, SSH key reused from Flux, outputs written to object status.
-
Kustomize configMapGenerator and secretGenerator
Generating ConfigMaps and Secrets from files with content-hash rolling updates, disableNameSuffixHash for Helm, env file sources, and HelmRelease valuesFrom.
-
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.
-
Kubernetes RBAC patterns: per-namespace roles in GitOps
Aggregated ClusterRoles for developer and devops, RoleBindings scoped per namespace managed by Flux, ClusterRoleBinding for monitoring read-only access.
-
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.
-
SealedSecrets: storing encrypted kubeconfigs in git
Bitnami SealedSecrets encrypt cluster credentials for safe git storage. Sealing workflow, namespace binding, update process, and controller troubleshooting.
-
Sealed Secrets: the full ceremony from install to cluster migration
kubeseal workflow: controller install, offline sealing with pub cert, cert backup procedures, rotating controller keys, and re-sealing all secrets when migrating to a new cluster.
-
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.