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
Currently, the API token is specified as a string literal in PSOPlugin object in purestorage.com/v1.
Since we check in all cluster objects in a git repository, this would mean that we have to expose the token to everyone who has read permission to the repository. This is not very secure.
Kubernetes secret is designed for managing sensitive information, and there are many options to allow us to safely version control secrets in git in encrypted form.
Can we allow the token to be referenced as a, for example, v1.SecretKeySelector?
The text was updated successfully, but these errors were encountered:
This just came up for us as well, we noticed that there was no way to get the API Token from a secret... It would require some restructuring, probably :(
Currently, the API token is specified as a string literal in
PSOPlugin
object inpurestorage.com/v1
.Since we check in all cluster objects in a git repository, this would mean that we have to expose the token to everyone who has read permission to the repository. This is not very secure.
Kubernetes secret is designed for managing sensitive information, and there are many options to allow us to safely version control secrets in git in encrypted form.
Can we allow the token to be referenced as a, for example, v1.SecretKeySelector?
The text was updated successfully, but these errors were encountered: