knative
/
docs
mirror of https://github.com/knative/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

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
This commit is contained in:
Izabela Gomes 2022-10-13 09:00:53 -04:00 committed by GitHub
parent 99ae375247
commit 84300936d0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/serving/using-auto-tls.md
View File

@ -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