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

Read license from file in tunnel client deployment vs from argument #66

Open
alexellis opened this issue Mar 10, 2020 · 0 comments
Open
Assignees

Comments

@alexellis
Copy link
Member

Read license from file in tunnel client deployment vs from argument

Expected Behaviour

I would like the secret to be read from a file i.e. a Kubernetes secret which is mounted, so that the secret can be updated without editing the deployments

Current Behaviour

If the license needs to be rotated, we have to edit each deployment in Kubernetes, or delete the deployment and have it recreated. The license also "leaks" via kubectl get deployment

Possible Solution

Create a secret for the inlets-pro license when deploying the operator, then bind this to each deployment. It may also be necessary to re-create the secret in each namespace where it is used by a tunnel deployment. I'm not sure that there's a way around this.

@alexellis alexellis self-assigned this Mar 10, 2020
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