-
Notifications
You must be signed in to change notification settings - Fork 24
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
Need the ability to specify the equivalent of root_cas: host in the ingress controller #369
Comments
|
Oh, neat. I didn't see this comment and apparently didn't actually read very much of the tunneldriver code I was messing with. Sounds like that solves the problem assuming the ssl certs directory isn't too hard to create. |
Still makes sense to have a setting like your PR to not need to deal with directories, but could be a quick-fix with existing release at least |
@jrobsonchase ideally we would make it more like the agent so the user doesn't have to change anything. While it may be possible to do, it creates an overhead with extra steps for making this work especially in managed k8s services like gke, eks etc where the user likely isn't customizing anything else on the worker nodes already. |
Is this in reference to the directory creation or adding Unless I missed something (which is entirely possible), we still require you to set |
@jrobsonchase What I meant was I think it's better to have a |
Kubernetes Version
latest
Helm Chart Version
latest
Helm Chart configuration
No response
What happened
When using a custom serverAddr like --set serverAddr="tunnel.us.connect.example.com:443" if that edge domain was created with a cert signed by letsencrypt, we need the ability to tell the ingress controller to trust the host's root CA store just like we do when using that custom serverAddr with the CLI agent.
We get this error:
What you think should happen instead
No response
How to reproduce
No response
The text was updated successfully, but these errors were encountered: