You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Using the Doppler provider requires that a static access token be generated and kept in the cluster to authorize the SecretStore to Doppler.
Describe the solution you'd like
Doppler now supports OIDC Service Account auth which would provide a significant improvement to secret access. So long as the k8s cluster has an OIDC provider enabled, it should be able to use a k8s ServiceAccount token to authenticate to Doppler as the configured doppler service-account.
Describe alternatives you've considered
Rotating access tokens, deploying them to cluster, and reflecting across required namespaces... this approach is complex, fragile, and less secure than identity-based access.
Is your feature request related to a problem? Please describe.
Using the Doppler provider requires that a static access token be generated and kept in the cluster to authorize the SecretStore to Doppler.
Describe the solution you'd like
Doppler now supports OIDC Service Account auth which would provide a significant improvement to secret access. So long as the k8s cluster has an OIDC provider enabled, it should be able to use a k8s ServiceAccount token to authenticate to Doppler as the configured doppler service-account.
Describe alternatives you've considered
Rotating access tokens, deploying them to cluster, and reflecting across required namespaces... this approach is complex, fragile, and less secure than identity-based access.
Additional context
https://docs.doppler.com/docs/service-account-identities
The text was updated successfully, but these errors were encountered: