Clarify requirements for permitted x509 extensions #1541
Merged
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.
Whilst implementing the recent changes in #1400 in kubernetes/kubernetes, we discovered an ambiguity in the wording for the requirements around x509 extensions for
kubelet-serving
specified CertificateSigningRequests.This patch amends the KEP according to the actual requirements/expectations, based on how the kubelet actually behaves: https://github.com/kubernetes/kubernetes/blob/d90dd93855ab6c3ccda73dfbd3d19c81f56abca5/pkg/kubelet/certificate/kubelet.go#L89-L103
/cc @liggitt
/assign @enj