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

http: TLS handshake error from ip:44184: remote error: tls: bad certificate #17

Open
wanminny opened this issue Jul 19, 2021 · 6 comments

Comments

@wanminny
Copy link

webhook pod logs

{"level":"info","ts":1626676817.2678869,"logger":"kubebuilder.webhook","msg":"starting the webhook server."}
2021/07/19 06:40:55 http: TLS handshake error from ip:44182: remote error: tls: bad certificate
2021/07/19 06:40:55 http: TLS handshake error from ip:44184: remote error: tls: bad certificate

@wanminny
Copy link
Author

{"level":"info","ts":1626676816.6311789,"logger":"cmd","msg":"Starting the Cmd."}
{"level":"info","ts":1626676816.7314544,"logger":"kubebuilder.webhook","msg":"installing webhook configuration in cluster"}
{"level":"info","ts":1626676816.8323817,"logger":"kubebuilder.admission.cert.writer","msg":"cert is invalid or expiring, regenerating a new one"}
{"level":"info","ts":1626676817.2678869,"logger":"kubebuilder.webhook","msg":"starting the webhook server."}
2021/07/19 06:40:55 http: TLS handshake error from ip:44182: remote error: tls: bad certificate
2021/07/19 06:40:55 http: TLS handshake error from ip:44184: remote error: tls: bad certificate

@sabre1041
Copy link
Collaborator

@wanminny would you be able to provide some more information into your environmentm/deployment

@wanminny
Copy link
Author

@wanminny would you be able to provide some more information into your environmentm/deployment

sorry
k8s v1.20+
yaml:
https://github.com/wanminny/podpreset-webhook/tree/master/deploy
thx.

@sabre1041
Copy link
Collaborator

@wanminny I noticed that your fork has not been updated recently. The operator was greatly improved as part of the migration to Operator SDK 1.0. Would you be able to resync your fork to see if it resolves your issues?

@wanminny
Copy link
Author

@wanminny I noticed that your fork has not been updated recently. The operator was greatly improved as part of the migration to Operator SDK 1.0. Would you be able to resync your fork to see if it resolves your issues?

the new version is the same as my fork branch.
notice : k8s 1.18 is ok ,use the old my fork branch.

@sabre1041
Copy link
Collaborator

sabre1041 commented Jul 26, 2021

@wanminny looking at your fork, it notes that your branch is 6 commits behind the upstream repository

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