Backport of Update helm standalone TLS doc for k8s 1.22 into release/1.11.x #16045
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.
Backport
This PR is auto-generated from #16029 to be assessed for backporting due to the inclusion of the label backport/1.11.x.
The below text is copied from the body of the original PR.
The
CertificateSigningRequest
forv1beta1
API is no longeravailable, and now requires the
signerName
parameter.Many thanks to @DavidRBanks for the helpful notes in
hashicorp/vault-helm#243 (comment)
I tested this on Kubernetes 1.21 and 1.24. I also adjusted the
tr
command to work better on macOS (and still works fine on Linux).
Overview of commits