Editing Kube-root-ca.crt configMap
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 6: | Line 6: | ||
Note: | Note: | ||
Even though the custom [[CA certificate]] may be included in the filesystem (in the ConfigMap kube-root-ca.crt), you should not use that | Even though the custom [[CA certificate]] may be included in the filesystem (in the ConfigMap kube-root-ca.crt), you should not use that | ||
− | certificate authority for any purpose other than to verify internal Kubernetes endpoints. An example of an internal | + | certificate authority for any purpose other than to verify internal Kubernetes endpoints. An example of an internal Kubernetes endpoint is |
+ | the Service named kubernetes in the default namespace. | ||
If you want to use a custom certificate authority for your workloads, you should generate that CA separately, and distribute its CA certificate using a ConfigMap that your pods have access to read. | If you want to use a custom certificate authority for your workloads, you should generate that CA separately, and distribute its CA certificate using a ConfigMap that your pods have access to read. |
Advertising: