-
Notifications
You must be signed in to change notification settings - Fork 144
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
Add custom certificate authority, to run behing a corporate firewall #4258
Comments
I am in the same situation, but it works. I did do following:
Following environment variables can be used I believe:
I would bet on the |
I've tried to use the NODE_EXTRA_CA_CERTS pointing to a pem file with all custom / local PKI certificates, to no avail : it still fails with "self signed certificate" error. In fact, I have to use the dreaded "NODE_TLS_REJECT_UNAUTHORIZED=0" to suppress all errors regarding bad certificates. But the bad news is that even with the setting above and no more self signed error, the connection to the cluster is still failing when I click on the button to connect to one of my context, with a "HTTP Error: HTTP request failed" and no more details or log entries. Please note that kubectl or k9s are working fine from the same environment, without any custom parameter / environment variable. I'm totally lost, as I don't have any specifics about what's going on. Is there a way to have more details about the error ? |
Describe the enhancement you'd like to see
I'm running Monokle behind a corporate proxy (Global Protect) that transparently manage all connections. So everything certificates from internet seems to be signed by the proxy's own authority. This works if the tool you're using (browser, jvm etc.) is aware of this custom authority.
I need to have a way to add this CA to Monokle in order to be able to work with it. Currently, Monokle is totally useless.
Additional context
There is no way I can disable or change the proxy, this is a corporate choice and mandatory config.
The text was updated successfully, but these errors were encountered: