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

Retry creation of certs with backoff and eventually abort (exit 1) upon error #126

Open
abalaven opened this issue Nov 17, 2020 · 1 comment

Comments

@abalaven
Copy link
Contributor

The other possibility I see for improvement here would be to retry with backoff and eventually abort (exit 1) upon error. This way it would be eventually consistent during a kube-apiserver outage.

Originally posted by @kd7lxl in #120 (comment)

@abalaven abalaven changed the title Retry with backoff and eventually abort (exit 1) upon error Retry creation of certs with backoff and eventually abort (exit 1) upon error Nov 17, 2020
@drewwells
Copy link
Contributor

Does the provision.sh script still need to check for secrets against k8s api? The secrets are created by cert-manager and can be mounted. The script then would open up the TLS certificates and do necessary kubeadm commands to create k8s api certificates.

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