Add support for custom certificate life/expiration. #3217
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request adds support to RKE to allow the configuration of certificate lifetime/expiration to support typical corporate requirements for shorter certificate expiration.
This change acknowledges that the default certificate lifetime for cluster certificates is ~10 years and makes no change to that default. Instead it adds support for a
cluster.yml
configuration option calledcertificate_lifetime
. Thecertificate_lifetime
option accepts an integer being a number of days from the current date for which certificates will be valid. This logic is respected during both the creation of a new cluster or during certificate rotation. This modification does not make any changes to the CA's created by RKE.