Shared Secrets Workload ID
Business Critical Plan Feature
This is a Business Critical Plan feature. For more information, see our pricing plans or contact our sales team.
Prerequisites
To set up a workload-identity, you'll need:
- A self-hosted Space cluster
- Administrator access in your cloud provider
- Helm and
kubectl
About the Shared Secrets component
Configuration
Verify your configuration
After you apply the configuration use kubectl to verify the service account
has the correct annotation:
kubectl get serviceaccount external-secrets-controller -n ${YOUR_CONTROL_PLANE_NAMESPACE} -o yaml
Restart workload
kubectl rollout restart deployment external-secrets
Use cases
Next steps
Now that you have workload identity configured for the shared secrets component, visit the Shared Secrets guide for more information.
Other workload identity guides are: