Skip to content
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

Explicitly point out not installing ns-cert component for http01 challenge #2890

Merged
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion docs/serving/using-auto-tls.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,8 @@ Knative supports the following Auto TLS modes:

- In this type, your cluster does not need to be able to talk to your DNS server. You just
need to map your domain to the IP of the cluser ingress.
- When using HTTP-01 challenge, **a certificate will be provisioned per Knative Service.** Certificate provision per namespace is not supported when using HTTP-01 challenge.
- When using HTTP-01 challenge, **a certificate will be provisioned per Knative Service.**
- **HTTP-01 does not support provisioning a certificate per namespace.**

## Before you begin

Expand Down Expand Up @@ -154,6 +155,9 @@ and which DNS provider validates those requests.

If you choose to use the mode of provisioning certificate per namespace, you need to install `networking-ns-cert` components.

**IMPORTANT:** Provisioning a certificate per namespace only works with DNS-01
challenge. This component cannot be used with HTTP-01 challenge.

abrennan89 marked this conversation as resolved.
Show resolved Hide resolved
1. Determine if `networking-ns-cert` deployment is already installed by
running the following command:

Expand Down