From 7697eb514668a7abb6d3c059d38bf76fc7d1248b Mon Sep 17 00:00:00 2001 From: Peter Lee Date: Thu, 20 Apr 2017 19:11:26 +0800 Subject: [PATCH] Update link --- docs/tasks/tls/managing-tls-in-a-cluster.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tasks/tls/managing-tls-in-a-cluster.md b/docs/tasks/tls/managing-tls-in-a-cluster.md index 57e3462ea6..161093dbba 100644 --- a/docs/tasks/tls/managing-tls-in-a-cluster.md +++ b/docs/tasks/tls/managing-tls-in-a-cluster.md @@ -19,7 +19,7 @@ cluster and is distributed as a secret attached to default service accounts. Optionally, your workloads can use this CA to establish trust. Your application can request a certificate signing using the `certificates.k8s.io` API using a protocol that is similar to the -[ACME draft](https://letsencrypt.github.io/acme-spec/). +[ACME draft](https://github.com/ietf-wg-acme/acme/). ## Trusting TLS in a Cluster