External Secrets Operator
Synchronizes secrets from external stores into Kubernetes.
Component Category
Access and security / secret management
Component Description
External Secrets Operator (ESO) reads secret data from external providers (cloud key vaults, HashiCorp Vault, AWS Secrets Manager, and others) and creates native Kubernetes Secret resources. It uses ExternalSecret and SecretStore custom resources to define what to sync and where from.
Why It Is Used
In BullSequana AI, External Secrets Operator allows the platform to integrate with external secret management systems already in use by the organization. This avoids duplicating secret material across systems and supports enterprise secret governance policies without requiring changes to how platform components consume secrets.
With the external-vault secrets backend, External Secrets Operator delivers the rendered application secrets from a customer-managed Vault, and the manifests repository holds no secret values. Bootstrap credentials and Kubernetes-generated service-account tokens are separate. The platform configuration provides a Vault backend; other upstream ESO providers are not turnkey platform backends. See External Vault secrets.
Learn More
Deployment notes
External Secrets Operator deploys into the external-secrets namespace in the common tier. It runs one operator replica, one webhook replica, and one certificate controller replica. The certificate controller manages the webhook TLS certificate.
With the default sealed-secrets backend, External Secrets Operator deploys at sync wave 12, the last common-tier wave, which it shares with the telemetry query gateway, and the platform renders no secret store.
With the external-vault backend, it deploys at sync wave 1 so it runs before the components whose secrets it delivers. The platform renders one ClusterSecretStore, vault-store by default, that reads from the configured Vault endpoint with a token from a pre-created Kubernetes Secret. Its images are pulled with a registry secret created by bsqai apply-registry-secret external-secrets before the first sync.
Interacts With
Vault, the customer-managed secret store that ESO reads with theexternal-vaultbackend.- Platform workloads, which consume the Kubernetes
Secretresources that ESO creates with theexternal-vaultbackend.