https://wolkwacht.nl/tags/gitops/ Recent content in GitOps on Wolkwacht https://wolkwacht.nl/images/branding/feature-image.png https://wolkwacht.nl/images/branding/feature-image.png Hugo en-us Wed, 09 Sep 2026 00:00:00 +0000 https://wolkwacht.nl/posts/2026-09-05_secrets-management-showdown--azure-key-vault-csi-driver-vs-external-secrets-operator/ Wed, 09 Sep 2026 00:00:00 +0000 https://wolkwacht.nl/posts/2026-09-05_secrets-management-showdown--azure-key-vault-csi-driver-vs-external-secrets-operator/ <p><img alt="Two secrets-management paths lead from a secure vault into Kubernetes workloads" loading="lazy" src="https://wolkwacht.nl/images/2026/feature.svg"></p> <p>The real question is not whether to use the Azure Key Vault provider for the Secrets Store CSI Driver or the External Secrets Operator (ESO). Instead, it&rsquo;s whether your workload should access secret data as <strong>mounted files</strong> or via <strong>native Kubernetes Secret objects</strong>.</p> <p>That choice influences application design, rotation, incident handling, RBAC, observability, Helm compatibility, and GitOps. In short: <strong>CSI offers a more secure default for applications that consume files; ESO provides a more practical platform default when Kubernetes-native compatibility is a priority.</strong> This decision involves both GitOps and security considerations.</p> https://wolkwacht.nl/posts/gitops-on-azure-kubernetes-service-building-a-production-ready-platform-with-flux/ Wed, 18 Mar 2026 07:42:06 +0000 https://wolkwacht.nl/posts/gitops-on-azure-kubernetes-service-building-a-production-ready-platform-with-flux/ Kubernetes platforms seldom fail due to the technology itself; instead, failures are usually caused by operational issues.