Improve note on "Manage TLS Certificates": Replace "custom CA certificate" with "root CA certificate" for clarity

[frasmarco]

in the note:

Note:

Even though the custom CA certificate may be included in the filesystem (in the ConfigMap kube-root-ca.crt),

I think "custom CA certificate" should be better rewritten as "root CA certificate" for clarity.

[k8s-ci-robot]

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[dipesh-rawat]

Page reported in issue (based on the title): https://kubernetes.io/docs/tasks/tls/managing-tls-in-a-cluster/
/language en

[dipesh-rawat]

/retitle Improve note on "Manage TLS Certificates": Replace "custom CA certificate" with "root CA certificate" for clarity
/sig auth cluster-lifecycle

[frasmarco]

@dipesh-rawat This is not related to auth or cluster lifecycle SIGs, those aren't cluster certificates but application. "These CA and certificates can be used by your workloads to establish trust." I think the only SIG involved is documetation

[sftim]

Even though the custom CA certificate may be included in the filesystem (in the ConfigMap kube-root-ca.crt),

“custom” is not a synonym for “root”. We might want to write “custom trust anchor (the root certificate)”, or something like that. Although the ConfigMap is named kube-root-ca.crt, its key role is to provide a trust anchor (and, despite the name, I think that it can actually be an intermediate CA).

Which web page needs amending? Can you provide the URL @frasmarco?

[sftim]

/triage needs-information