ClusterSecretStore Resource
What you'll learn: How to configure cluster-wide ClusterSecretStores so multiple namespaces can share access to the same secret backend without duplicating configuration.
The Core Idea
In the previous lesson, you learned about SecretStore, which connects the External Secrets Operator to a backend (like AWS Secrets Manager or HashiCorp Vault) within a single namespace. But what if you have dozens of namespaces all needing to fetch secrets from the same backend? Copying the same SecretStore into every namespace is tedious and error-prone.
Enter ClusterSecretStore: it's the cluster-wide version of SecretStore. You define it once, and any namespace in your cluster can reference it to pull secrets from the shared backend.
Think of It Like This
Imagine a university library card system. A SecretStore is like a department-specific card that only works in the Engineering Library. A ClusterSecretStore is like a universal campus card—any student (namespace) can use it to access the central library (secret backend).
When to Use ClusterSecretStore
- Centralized backend configuration: One team manages the connection to AWS Secrets Manager, and all application teams reference it.
- Reduced duplication: No need to copy credentials or endpoint URLs into every namespace.
- Simplified RBAC: Control who can create cluster-wide resources separately from namespace-scoped ones.
How It Differs from SecretStore
| Feature | SecretStore | ClusterSecretStore |
|---|---|---|
| Scope | Single namespace | Entire cluster |
| Referenced by | ExternalSecret in same namespace | ExternalSecret in any namespace |
| API kind | SecretStore | ClusterSecretStore |
Key Takeaway: ClusterSecretStore enables shared, centralized secret backend access across all namespaces, eliminating configuration duplication and simplifying management.