Document the use of the HTTP01 Gateway API solver#625
Document the use of the HTTP01 Gateway API solver#625jetstack-bot merged 6 commits intocert-manager:release-nextfrom
Conversation
|
Skipping CI for Draft Pull Request. |
JoshVanL
left a comment
There was a problem hiding this comment.
Couple comments from me. Looks like this needs some kind of rebasing :)
6518364 to
ed223e5
Compare
|
✔️ Deploy Preview for cert-manager-website ready! 🔨 Explore the source changes: eaefa68 🔍 Inspect the deploy log: https://app.netlify.com/sites/cert-manager-website/deploys/61138ab369bd5d000984f808 😎 Browse the preview: https://deploy-preview-625--cert-manager-website.netlify.app |
ed223e5 to
4e5ce0f
Compare
4e5ce0f to
ac8e0e3
Compare
Signed-off-by: Maël Valais <mael@vls.dev>
Signed-off-by: Maël Valais <mael@vls.dev>
ac8e0e3 to
f29a49d
Compare
f29a49d to
1d42ae2
Compare
Signed-off-by: Maël Valais <mael@vls.dev>
1d42ae2 to
a007acf
Compare
Signed-off-by: Maël Valais <mael@vls.dev>
fd00880 to
f373024
Compare
This is the feature gate name that was picked in cert-manager/cert-manager#4310. Signed-off-by: Maël Valais <mael@vls.dev>
|
While writing this PR, I started writing a Getting started guide. I don't know where to publish this or whether it makes sense to publish it. Next steps:
|
| solving the HTTP-01 challenge. These labels must match one of the Gateway | ||
| resources on your cluster. The matched Gateway have a listener on port 80. |
There was a problem hiding this comment.
What happens if no Gateways match?
There was a problem hiding this comment.
I added the following note:
Note that when the labels do not match any Gateway on your cluster, cert-manager will create the temporary HTTPRoute challenge and nothing will happen.
c8a6d0b to
8f5db75
Compare
Signed-off-by: Maël Valais <mael@vls.dev> Co-authored-by: JoshVanL <vleeuwenjoshua@gmail.com>
8f5db75 to
eaefa68
Compare
|
Done! |
| ```sh | ||
| helm upgrade --install cert-manager jetstack/cert-manager --namespace cert-manager \ | ||
| --set "extraArgs={--feature-gates=ExperimentalGatewayAPISupport=true}" | ||
| ``` |
There was a problem hiding this comment.
Random thought: If you'd previously enabled the experimental CertificateRequestSupport would this command disable that. I do not propose changing this command, but it is worth thinking about how easy it is to change extraArgs values during an upgrade.
There was a problem hiding this comment.
Good point, I wish we could instead re-use the same flag multiple times:
helm upgrade --install cert-manager jetstack/cert-manager --namespace cert-manager \
--set extraArgs="--feature-gates=ExperimentalGatewayAPISupport=true" \
--set extraArgs="--feature-gates=ExperimentalCertificateRequestSupport=true"But the only way to set arrays from the command line is to use the syntax extraArgs={...,...} 😞
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: maelvls, wallrj The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This is the documentation for cert-manager/cert-manager#4276.