From 84300936d0dca0a8b9a5a95e7b7fd2229e123884 Mon Sep 17 00:00:00 2001 From: Izabela Gomes Date: Thu, 13 Oct 2022 09:00:53 -0400 Subject: [PATCH] Remove note about requirement to use http-protocol enabled with http01 challenge (#5261) * remove note about requirement to use http-protocol enabled with http-01 challenge * removed deprecated http-protocol option --- docs/serving/using-auto-tls.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/docs/serving/using-auto-tls.md b/docs/serving/using-auto-tls.md index b5e3ef892..eea98ad3b 100644 --- a/docs/serving/using-auto-tls.md +++ b/docs/serving/using-auto-tls.md @@ -41,7 +41,7 @@ Knative supports the following Auto TLS modes: 1. Using HTTP-01 challenge - - In this type, your cluster does not need to be able to talk to your DNS server. You must map your domain to the IP of the cluser ingress. + - In this type, your cluster does not need to be able to talk to your DNS server. You must map your domain to the IP of the cluster ingress. - When using HTTP-01 challenge, **a certificate will be provisioned per Knative Service.** - **HTTP-01 does not support provisioning a certificate per namespace.** @@ -249,7 +249,6 @@ Update the [`config-network` ConfigMap](https://github.com/knative/serving/blob/ Supported `http-protocol` values: - `Enabled`: Serve HTTP traffic. - - `Disabled`: Rejects all HTTP traffic. - `Redirected`: Responds to HTTP request with a `302` redirect to ask the clients to use HTTPS. @@ -273,9 +272,6 @@ Update the [`config-network` ConfigMap](https://github.com/knative/serving/blob/ ... ``` - !!! note - When using HTTP-01 challenge, `http-protocol` field has to be set to `Enabled` to make sure HTTP-01 challenge requests can be accepted by the cluster. - 1. Ensure that the file was updated successfully: ```bash