autotls/

README

This is the instruction about how to run Auto TLS E2E test under different configurations to test different use cases. For more details about Auto TLS feature, check out the Auto TLS feature documentation.

To run Auto TLS E2E test locally, run the following commands:

1. test case 1: testing per ksvc certificate provision with self-signed CA
   1. Run kubectl patch cm config-network -n knative-serving -p '{"data":{"namespace-wildcard-cert-selector": ""}}' to disable wildcards for namespaces
   2. kubectl delete kcert --all -n serving-tests
   3. kubectl apply -f test/config/autotls/certmanager/selfsigned/
   4. go test -v -tags=e2e -count=1 -timeout=600s ./test/e2e/autotls/... -run ^TestTLS
2. test case 2: testing per namespace certificate provision with self-signed CA
   1. kubectl delete kcert --all -n serving-tests
   2. kubectl apply -f test/config/autotls/certmanager/selfsigned/
   3. Run kubectl patch cm config-network -n knative-serving -p '{"data":{"namespace-wildcard-cert-selector": "{}"}}' to enable wildcards for all namespaces
   4. go test -v -tags=e2e -count=1 -timeout=600s ./test/e2e/autotls/... -run ^TestTLS
3. test case 3: testing per ksvc certificate provision with HTTP challenge
   1. Run kubectl patch cm config-network -n knative-serving -p '{"data":{"namespace-wildcard-cert-selector": ""}}' to disable wildcards for namespaces
   2. kubectl delete kcert --all -n serving-tests
   3. kubectl apply -f test/config/autotls/certmanager/http01/
   4. export SERVICE_NAME=http01
   5. kubectl patch cm config-domain -n knative-serving -p '{"data":{"<your-custom-domain>":""}}'
   6. Add a DNS A record to map host http01.serving-tests.<your-custom-domain> to the Ingress IP.
   7. go test -v -tags=e2e -count=1 -timeout=600s ./test/e2e/autotls/... -run ^TestTLS