This documentation is for a release that is no longer maintained
See documentation for the latest supported version 3 or the latest supported version 4.第 3 章 Certificate types and descriptions
3.1. User-provided certificates for the API server 复制链接链接已复制到粘贴板!
3.1.1. Purpose 复制链接链接已复制到粘贴板!
The API server is accessible by clients external to the cluster at api.<cluster_name>.<base_domain>. You might want clients to access the API server at a different host name or without the need to distribute the cluster-managed certificate authority (CA) certificates to the clients. The administrator must set a custom default certificate to be used by the API server when serving content.
3.1.2. Location 复制链接链接已复制到粘贴板!
The user-provided certificates must be provided in a kubernetes.io/tls type Secret in the openshift-config namespace. Update the API server cluster configuration, the apiserver/cluster resource, to enable the use of the user-provided certificate.
3.1.3. Management 复制链接链接已复制到粘贴板!
User-provided certificates are managed by the user.
3.1.4. Expiration 复制链接链接已复制到粘贴板!
API server client certificate expiration is less than five minutes.
User-provided certificates are managed by the user.
3.1.5. Customization 复制链接链接已复制到粘贴板!
Update the secret containing the user-managed certificate as needed.