-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Update helm standalone TLS doc for k8s 1.22 #16029
Conversation
The `CertificateSigningRequest` for `v1beta1` API is no longer available, 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).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! Just a couple suggestions.
export TMPDIR=/tmp | ||
|
||
# CSR_NAME will be the name of our certificate signing request as seen by Kubernetes. | ||
export CSR_NAME=vault-csr |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
May want to update the opening sentence here since it states There are three variables...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Thanks! |
Update helm standalone TLS doc for k8s 1.22 The `CertificateSigningRequest` for `v1beta1` API is no longer available, 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).
Update helm standalone TLS doc for k8s 1.22 The `CertificateSigningRequest` for `v1beta1` API is no longer available, 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). Co-authored-by: Christopher Swenson <swenson@swenson.io>
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).