-
Notifications
You must be signed in to change notification settings - Fork 377
Add doc content for new Ingress annotation http01-ingress-ingressclassname
#1848
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
base: release-next
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -27,12 +27,20 @@ This is useful for keeping compatibility with the `ingress-gce` component. | |||||||||||||||||||||
| ## acme.cert-manager.io/http01-ingress-class | ||||||||||||||||||||||
| - [Ingress](../usage/ingress.md) | ||||||||||||||||||||||
|
|
||||||||||||||||||||||
| this annotation allows you to configure the ingress class that will be used to | ||||||||||||||||||||||
| solve challenges for this ingress. Customizing this is useful when you are | ||||||||||||||||||||||
| trying to secure internal services, and need to solve challenges using a | ||||||||||||||||||||||
| different ingress class to that of the ingress. If not specified and the | ||||||||||||||||||||||
| `acme-http01-edit-in-place` annotation is not set, this defaults to the ingress | ||||||||||||||||||||||
| class defined in the Issuer resource. | ||||||||||||||||||||||
| this annotation allows you to configure the `kubernetes.io/ingress.class` that will be | ||||||||||||||||||||||
| used to solve challenges for this ingress. Customizing this is useful when you are trying | ||||||||||||||||||||||
| to secure internal services, and need to solve challenges using a different ingress class | ||||||||||||||||||||||
| to that of the ingress. If not specified and the `acme-http01-edit-in-place` annotation is | ||||||||||||||||||||||
| not set, this defaults to the `http01.ingress.class` defined in the Issuer resource. | ||||||||||||||||||||||
|
|
||||||||||||||||||||||
| ## acme.cert-manager.io/http01-ingress-ingressclassname | ||||||||||||||||||||||
| - [Ingress](../usage/ingress.md) | ||||||||||||||||||||||
|
|
||||||||||||||||||||||
| this annotation allows you to configure the `spec.ingressClassName` that will be | ||||||||||||||||||||||
| used to solve challenges for this ingress. Customizing this is useful when you are trying | ||||||||||||||||||||||
| to secure internal services, and need to solve challenges using a different ingress class | ||||||||||||||||||||||
| to that of the ingress. If not specified and the `acme-http01-edit-in-place` annotation is | ||||||||||||||||||||||
| not set, this defaults to the `http01.ingress.ingressClassName` defined in the Issuer resource. | ||||||||||||||||||||||
|
Comment on lines
+39
to
+43
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. nitpick (minor): (As above) I think we should start with a capital letter here, and I don't think we need to say "this annotation" because I think in context it's clear that it's an annotation. (I can see you adapted this from elsewhere in the docs where it's already present, but I think it's worth writing differently anyway!)
Suggested change
|
||||||||||||||||||||||
|
|
||||||||||||||||||||||
| ## cert-manager.io/allow-direct-injection | ||||||||||||||||||||||
| - `Secret` | ||||||||||||||||||||||
|
|
||||||||||||||||||||||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -3,7 +3,7 @@ title: Annotated Ingress resource | |
| description: 'cert-manager usage: Kubernetes Ingress' | ||
| --- | ||
|
|
||
| > **apiVersion:** networking.k8s.io/v1 | ||
| > **apiVersion:** networking.k8s.io/v1 | ||
| > **kind:** Ingress | ||
|
|
||
| <div style={{textAlign: "center"}}> | ||
|
|
@@ -89,11 +89,19 @@ trigger `Certificate` resources to be automatically created: | |
| container. | ||
|
|
||
| - `acme.cert-manager.io/http01-ingress-class`: this annotation allows you to | ||
| configure the ingress class that will be used to solve challenges for this | ||
| ingress. Customizing this is useful when you are trying to secure internal | ||
| configure the `kubernetes.io/ingress.class` that will be used to solve challenges | ||
| for this ingress. Customizing this is useful when you are trying to secure internal | ||
| services, and need to solve challenges using a different ingress class to that | ||
| of the ingress. If not specified and the `acme-http01-edit-in-place` annotation | ||
| is not set, this defaults to the ingress class defined in the Issuer resource. | ||
| is not set, this defaults to the `http01.ingress.class` defined in the Issuer resource. | ||
|
|
||
| - `acme.cert-manager.io/http01-ingress-ingressclassname`: this annotation allows you to | ||
| configure the `spec.ingressClassName` that will be used to solve challenges | ||
| for this ingress. Customizing this is useful when you are trying to secure internal | ||
| services, and need to solve challenges using a different ingress class to that | ||
| of the ingress. If not specified and the `acme-http01-edit-in-place` annotation | ||
| is not set, this defaults to the `http01.ingress.ingressClassName` defined in the | ||
| Issuer resource. | ||
|
Comment on lines
91
to
+104
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. comment: I'd prefer if this wasn't written "this annotation..." but I totally recognise that's how it already is, and we definitely shouldn't rework this page in this PR. This is really good, thank you 👍 |
||
|
|
||
| - `acme.cert-manager.io/http01-edit-in-place: "true"`: this controls whether the | ||
| ingress is modified 'in-place', or a new one is created specifically for the | ||
|
|
||
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.
nitpick (minor): I think we should start with a capital letter here, and I don't think we need to say "this annotation" because I think in context it's clear that it's an annotation.
(I can see you adapted this from elsewhere in the docs where it's already present, but I think it's worth writing differently anyway!)