-
Notifications
You must be signed in to change notification settings - Fork 37
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
certificate verify failed issue when using Get Namespaced Pod Exec #123
Comments
Yeah your workaround is way to go, it does the current setting underneath so it is preferred, Please take a look at v0.8.1 at let me know if it works for you. |
Thanks for the release @m-wcislo! However, removing the line https://github.com/devopsspiral/KubeLibrary/pull/124/files#diff-65edc7c7cbe7902bb5d18f0b4555bbf308e8cac89745ce248bec177fd9a9b334L279 introduced a regression. For example, using the keyword
Could it be reverted please? |
ok, reverted in 0.8.2, need to take closer look. |
Thank you! From our tests, keeping both if not self.cert_validation:
self.__dict__[reference].api_client.rest_client.pool_manager.connection_pool_kw['cert_reqs'] = ssl.CERT_NONE
self.__dict__[reference].api_client.configuration.verify_ssl = False was working as expected. |
Actually it is reverted in 0.8.3. yeah need to track down how the setting is propagated, latest setting should set both |
Ok, did some testing and cannot really reproduce it on my end, so have couple questions:
This is the easiest way to make your connection trust the API server cert, without need of use cert_validation=False |
When using the Get Namespaced Pod Exec keywork on a k8s cluster using a custom CA, the following error occurs :
Other keywords (Read Namespaced Pod Status, List Namespaced Pod By Pattern ...) are working as expected.
As a quick fix, I'm adding the following line in the _add_api method of the library :
Am I missing something regarding the library configuration ?
Versions :
KubeLibrary :
The text was updated successfully, but these errors were encountered: