Vault Secrets Operator release notes
Review the new features and breaking changes in each release of the Vault Secrets Operator before you upgrade.
Vault Secrets Operator 2.0.0
Released: 2026-11-12
Breaking changes
Removed the
kube-rbac-proxysidecar: The Vault Secrets Operator Deployment no longer includes thekube-rbac-proxycontainer (quay.io/brancz/kube-rbac-proxy, orose-kube-rbac-proxyon OpenShift), so the operator no longer requires a second container image. The operator now serves the/metricsendpoint over HTTPS on port8443and runs the sameTokenReviewandSubjectAccessReviewauthentication and authorization checks itself. The metrics Service, its port, the ServiceMonitor, and the metrics RBAC are unchanged, so existing scrape configurations continue to work. Before you upgrade, review the following changes:- Prometheus Operator: Scraped metrics now carry the label
container="manager"instead ofcontainer="kube-rbac-proxy". Update any dashboards, alerts, or recording rules that filter on the old label value. - Invalid bearer tokens: Requests to
/metricswith an invalid bearer token now return HTTP500instead of401, and the operator logs the failure at the error level. - Helm: The chart no longer supports the
controller.kubeRbacProxy.*values and ignores them if they are set. Remove them from your values files, and usecontroller.manager.resourcesto tune the operator's resources. - Kustomize: Remove any custom patches that target the
kube-rbac-proxycontainer. Otherwise, the patches add a broken container back to the Deployment.
Refer to Vault Secrets Operator telemetry, the
metricsServiceHelm values, and Install and upgrade the Vault Secrets Operator for more information.- Prometheus Operator: Scraped metrics now carry the label
New features
Issue certificates with cert-manager
: The Vault Secrets Operator can act as a cert-manager external issuer with the newEnterpriseVaultIssuerandVaultClusterIssuerresources. Applications request certificates with standard cert-managerCertificateresources, and the operator signs each request with the Vault PKI secrets engine, using the sameVaultConnectionandVaultAuthresources that it uses to sync secrets. The issuers require Vault Enterprise.To get started, refer to Set up the cert-manager issuer. To move existing certificates from the Vault issuer built into cert-manager, refer to Migrate from the cert-manager Vault issuer. For the full resource specification, refer to
VaultIssuerandVaultClusterIssuerin the API reference.
Bug fixes
VaultStaticSecretrollout restarts: The operator now restartsrolloutRestartTargetsonly when the secret data changes, not when a.specchange leaves the data unchanged.