CredentialStore selects the credential backend used for MCP on-behalf-of (OBO) user grants in its
own namespace, overriding the cluster default. ClusterCredentialStore is the cluster-wide default,
used for any namespace without its own CredentialStore. Both share the same spec/status. Modeled on
the External Secrets Operator’s SecretStore / ClusterSecretStore, the backend is a config choice, not a
rebuild. Enforcement point: the token-service, which constructs the selected
backend and does the OAuth refresh; agent pods hold no backend credentials. When no
ClusterCredentialStore exists, the token-service defaults to the kubernetes backend. Only stores
named default are read; a store with any other name is ignored without an error.
Exactly one provider must be set. This is a discriminated union — set kubernetes, postgres,
or remote (never more than one). The schema also accepts openbao, but no openbao backend is
built: a store that selects it fails every credential resolution. For OpenBao, use postgres with
openBaoTransit custody.
Reserved. No component writes it: the token-service only reads stores, so nothing reports whether a backend was selected or reachable. A backend that cannot be constructed fails credential resolution for the namespaces that select it.