Skip to content
New issue

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

The operator should support using a different set of NATS credentials for communicating with wadm #17

Open
protochron opened this issue Apr 8, 2024 · 0 comments

Comments

@protochron
Copy link
Contributor

Add a configuration option so that we can load a NATS credentials file stored as a secret and use it to configure the client we use to communicate with the NATS cluster. These credentials should only be used to configure the operator's consumer and the stream that we create when bootstrapping. If a WasmCloudHostConfig references a secret that has NATS credentials then the operator should use those credentials when creating a client to manage wasmCloud applications. Otherwise it should fall back to either its own credentials or using unauthenticated calls.

@protochron protochron reopened this Apr 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant