We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VMAuth, VMUser, VMOperator
We have enabled authentication between the VMAgents and the VMCluster, and using VMUser to generate the password.
The text was updated successfully, but these errors were encountered:
moved operator specific issue to operator repo
Sorry, something went wrong.
It's a good question. Currently, operator has an assumption, that secrets are protected (by kubernetes RBAC) and stored at encrypted storage (https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/).
secrets
There is no way to encrypt it at operator level, because vmauth must be aware of it and perform decryption before loading sensitive data in-memory.
As workaround, it's possible to use external configuration for VMAuth and use 3rd party secret providers ( like vault).
external
VMAuth
No branches or pull requests
Is your question request related to a specific component?
VMAuth, VMUser, VMOperator
Describe the question in detail
We have enabled authentication between the VMAgents and the VMCluster, and using VMUser to generate the password.
Troubleshooting docs
The text was updated successfully, but these errors were encountered: