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

Certificate Errors when using #220

Open
jed-t5417 opened this issue Jun 1, 2023 · 3 comments
Open

Certificate Errors when using #220

jed-t5417 opened this issue Jun 1, 2023 · 3 comments

Comments

@jed-t5417
Copy link

Using against internal lab. Unclear whether this is failing due to certificates used in this plugin, or if it doesnt like the certificates used in the lab which will be self signed.

kubectl view-allocations -g resource
2023-06-01T15:21:28.377339Z ERROR failed with error error trying to connect: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1921:: self signed certificate in certificate chain
Error:
0: Failed to list nodes
1: HyperError: error trying to connect: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1921:: self signed certificate in certificate chain
2: error trying to connect: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1921:: self signed certificate in certificate chain
3: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1921:: self signed certificate in certificate chain
4: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1921:
5: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1921:

Location:
src/main.rs:47

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.

kubectl view-allocations -u
2023-06-01T15:22:42.695887Z ERROR failed with error error trying to connect: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1921:: self signed certificate in certificate chain
Error:
0: Failed to list nodes
1: HyperError: error trying to connect: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1921:: self signed certificate in certificate chain
2: error trying to connect: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1921:: self signed certificate in certificate chain
3: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1921:: self signed certificate in certificate chain
4: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1921:
5: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1921:

Location:
src/main.rs:47

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.

@robinkb
Copy link

robinkb commented Jun 2, 2023

I'm seeing this issue as well when running the latest version on Fedora Linux 38. I manually downloaded version 0.15.1, and that works fine.

(Love the plugin by the way, super useful)

@byroncollins
Copy link

I'm seeing this issue from the Windows 0.16.3 x86_64 version as well and downloading the previous version of 0.15.1 fixes my issue as well. The difference is however that our certificates are public and trusted.

@davidB
Copy link
Owner

davidB commented Sep 24, 2023

Can you give a try to version 0.17.x ?

(since version 0.17, the handling of SSL move from OpenSSL to rustls + few other bugfix on the underling kube library).

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

4 participants