External Secrets Operator Architecture
What you'll learn: How the External Secrets Operator bridges Kubernetes and external secret providers through its core resource types.
The Core Problem
You've learned that Kubernetes Secrets can be stored externally (lesson 1275). But how does Kubernetes actually fetch those secrets from AWS Secrets Manager, HashiCorp Vault, or Azure Key Vault? The External Secrets Operator (ESO) solves this through a clean, modular architecture.
The Three Key Resources
Think of ESO like a restaurant chain ordering from suppliers:
SecretStore and ClusterSecretStore
These define where to fetch secrets from—your "supplier contract."
- SecretStore: Namespace-scoped. Only ExternalSecrets in the same namespace can use it.
- ClusterSecretStore: Cluster-wide. Any ExternalSecret in any namespace can reference it.
Both specify connection details (endpoint, authentication) to external providers like AWS or Vault.
ExternalSecret
This defines what to fetch—your "order form."
An ExternalSecret references a SecretStore (or ClusterSecretStore) and specifies which secrets to pull and how to map them into a native Kubernetes Secret.
The Interaction Pattern
- You create a SecretStore pointing to your external provider
- You create an ExternalSecret that references that SecretStore
- ESO watches the ExternalSecret, connects to the provider via the SecretStore
- ESO fetches the secret data and creates/updates a standard Kubernetes Secret
- Your pods consume the Secret normally—they don't know it came from outside!
ESO runs as a controller, continuously syncing external values into Kubernetes Secrets based on your ExternalSecret definitions.
Key Takeaway: External Secrets Operator uses SecretStore/ClusterSecretStore to define provider connections and ExternalSecret resources to declare which external secrets should become Kubernetes Secrets—cleanly separating connection config from secret retrieval logic.