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

Configurable expire dates on certificates #57

Closed
anton-johansson opened this issue Aug 19, 2019 · 1 comment · Fixed by #63
Closed

Configurable expire dates on certificates #57

anton-johansson opened this issue Aug 19, 2019 · 1 comment · Fixed by #63
Assignees

Comments

@anton-johansson
Copy link
Collaborator

Currently all certificates expire 5 years after creation.

Do we want to utilize a parameter for this value? Also, maybe a separate parameter specifically for the common authority certificates for kube-apiserver and etcd, maybe also with a bit longer default?

Maybe also have another parameter for forcing recreation of common authorities, regenerate_ca_certificates=True (in additionl to regenerate_certificates).

When the time comes to renew certificates (common authorities specifically) it would be nice with a zero-downtime routine. I'll see if I can try to test this routine (as soon as I have time). If it only means downtime for state updates (such as Ingress controller config and node updates and similar), I think it's OK. As long as traffic are still routed properly to the containers.

@amimof amimof self-assigned this Feb 22, 2020
amimof pushed a commit that referenced this issue Feb 22, 2020
@amimof
Copy link
Owner

amimof commented Feb 22, 2020

PR #63 fixes this. It adds the certificate_expiry variable but regenerate_certificates variable is unchanged for now.

amimof pushed a commit that referenced this issue Feb 22, 2020
amimof pushed a commit that referenced this issue Feb 22, 2020
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

Successfully merging a pull request may close this issue.

2 participants