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

self signed certificate in certificate chain error in 1.0.0-rc4 #1827

Closed
rudyflores opened this issue Aug 1, 2024 · 2 comments
Closed

self signed certificate in certificate chain error in 1.0.0-rc4 #1827

rudyflores opened this issue Aug 1, 2024 · 2 comments

Comments

@rudyflores
Copy link

Describe the bug
A clear and concise description of what the bug is.

I receive the following error:

request to https://example?pretty=true failed, reason: self signed certificate in certificate chain

this was not appearing on previous versions of the kubernetes client, I also noticed it on 0.20.0 but had to upgrade due to vulnerability issues with request, is there a way to get rid of this error? I am logging into my cluster and generating a token just fine which used to work.

** Client Version **
e.g. 0.12.0

v1.0.0-rc4

** Server Version **
e.g. 1.19.1

v1.26.6

To Reproduce
Steps to reproduce the behavior:

run any request with kubernetes client, e.g:

await this.kc.readNamespace({
          name: this.kubeConfig.namespace,
          pretty: "true",
});

Expected behavior
A clear and concise description of what you expected to happen.

I should be able to make calls without errors about self-signed certs in cert chain.

** Example Code**
Code snippet for what you are doing

Environment (please complete the following information):

  • OS: [e.g. Windows, Linux] MacOS
  • NodeJS Version [eg. 10] v18.19.0
  • Cloud runtime [e.g. Azure Functions, Lambda]

Additional context
Add any other context about the problem here.

@rudyflores
Copy link
Author

rudyflores commented Aug 1, 2024

Re-opened this issue because I never got an answer whether this will be addressed or not, this makes the kubernetes client completely unusable on my environment.

old issue: #1509

@brendandburns
Copy link
Contributor

Closing this in favor of the original issue, next time you can use the /reopen command, or you can set the lifecycle to frozen to prevent it from being auto-closed.

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

2 participants