We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Please create an issue for removing (or adding comment about) --ignore-preflight-errors all and add the issue number here as a comment.
--ignore-preflight-errors all
Originally posted by @to-bar in Fix 'Join to Kubernetes cluster' task #2805 (comment)
We re-generate apiserver certificates here for issue [BUG] Kubectl client outside of HA/multi-master Epiphany cluster fails to connect to server with invalid certificate #1520. But in fact cert SANs patching should be moved to patching apiserver configuration in upgrade and executed here only after promotion to ha. Check kubeadm configuration.
To summarize:
Following cases will be covered:
Example of check: openssl x509 -in /etc/kubernetes/pki/apiserver.crt -text -noout | grep DNS:
openssl x509 -in /etc/kubernetes/pki/apiserver.crt -text -noout | grep DNS:
Condider adding block/rescue for certificates generation to handle failures:
DoD checklist
The text was updated successfully, but these errors were encountered:
Tested:
However, it is not recommended to renew certificates after executing kubeadm reset command as it may fail in some edge cases - documentation updated.
kubeadm reset
Sorry, something went wrong.
atsikham
przemyslavic
No branches or pull requests
Please create an issue for removing (or adding comment about)
--ignore-preflight-errors all
and add the issue number here as a comment.Originally posted by @to-bar in Fix 'Join to Kubernetes cluster' task #2805 (comment)
We re-generate apiserver certificates here for issue [BUG] Kubectl client outside of HA/multi-master Epiphany cluster fails to connect to server with invalid certificate #1520. But in fact cert SANs patching should be moved to patching apiserver configuration in upgrade and executed here only after promotion to ha. Check kubeadm configuration.
To summarize:
Following cases will be covered:
Example of check:
openssl x509 -in /etc/kubernetes/pki/apiserver.crt -text -noout | grep DNS:
Condider adding block/rescue for certificates generation to handle failures:
DoD checklist
The text was updated successfully, but these errors were encountered: