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
I'm using username and password authentication and would like to use the controller. I'm using ArgoCD so all my yamls are in my git repos.
One way I think is allowing the controller to interpolate env variables: nats-io/nack#76 (comment)
And then change the deployment.yaml file to accept extraSecretMounts. I could do the PR for this.
extraSecretMounts
Anyone using username/password authentication, gitops and wants to use the jetstream controller.
With gitops practices all the helm/yaml files are stored in git, so without this you would be exposing your creds.
No response
The text was updated successfully, but these errors were encountered:
This is an example using account.
apiVersion: jetstream.nats.io/v1beta2 kind: Account spec: name: <accountName> servers: - nats://<user>:<password>@<host>:<port>
apiVersion: jetstream.nats.io/v1beta2 kind: Stream spec: account: <accountName>
Sorry, something went wrong.
@hhk7734 with this the username and password would still be exposed because the account.yaml would also be in git
Do you use an external secret like a vault?
Using AWS secrets manager with external-secrets operator.
No branches or pull requests
What motivated this proposal?
I'm using username and password authentication and would like to use the controller. I'm using ArgoCD so all my yamls are in my git repos.
What is the proposed change?
One way I think is allowing the controller to interpolate env variables: nats-io/nack#76 (comment)
And then change the deployment.yaml file to accept
extraSecretMounts
. I could do the PR for this.Who benefits from this change?
Anyone using username/password authentication, gitops and wants to use the jetstream controller.
With gitops practices all the helm/yaml files are stored in git, so without this you would be exposing your creds.
What alternatives have you evaluated?
No response
The text was updated successfully, but these errors were encountered: