Fixed Hyperlinks for custom CA and dedicated CA.
This commit is contained in:
@@ -18,7 +18,7 @@ draft](https://github.com/ietf-wg-acme/acme/).
|
|||||||
|
|
||||||
{{< note >}}
|
{{< note >}}
|
||||||
Certificates created using the `certificates.k8s.io` API are signed by a
|
Certificates created using the `certificates.k8s.io` API are signed by a
|
||||||
[dedicated CA](#a-note-to-cluster-administrators). It is possible to configure your cluster to use the cluster root
|
[dedicated CA](#configuring-your-cluster-to-provide-signing). It is possible to configure your cluster to use the cluster root
|
||||||
CA for this purpose, but you should never rely on this. Do not assume that
|
CA for this purpose, but you should never rely on this. Do not assume that
|
||||||
these certificates will validate against the cluster root CA.
|
these certificates will validate against the cluster root CA.
|
||||||
{{< /note >}}
|
{{< /note >}}
|
||||||
@@ -42,7 +42,7 @@ install it via your operating system's software sources, or fetch it from
|
|||||||
|
|
||||||
## Trusting TLS in a cluster
|
## Trusting TLS in a cluster
|
||||||
|
|
||||||
Trusting the [custom CA](#a-note-to-cluster-administrators) from an application running as a pod usually requires
|
Trusting the [custom CA](#configuring-your-cluster-to-provide-signing) from an application running as a pod usually requires
|
||||||
some extra application configuration. You will need to add the CA certificate
|
some extra application configuration. You will need to add the CA certificate
|
||||||
bundle to the list of CA certificates that the TLS client or server trusts. For
|
bundle to the list of CA certificates that the TLS client or server trusts. For
|
||||||
example, you would do this with a golang TLS config by parsing the certificate
|
example, you would do this with a golang TLS config by parsing the certificate
|
||||||
|
|||||||
Reference in New Issue
Block a user