2ac452053c
Updated formatting issues Included inputs from Gerrit rview https://review.opendev.org/c/starlingx/docs/+/847215; https://review.opendev.org/c/starlingx/docs/+/888578 Updated Patchset 1 comments and added the limitation in Created Include file to add the Limitation Change-Id: I59aabd2bc67c4f2820b75ece7f6a0557729adc9e Signed-off-by: Juanita Balaraj <juanita.balaraj@windriver.com>
20 KiB
HTTPS and Certificates Management Overview
Certificates are required for secure HTTPS access and authentication on platform.
This table lists all the platform certificates, and indicates which certificates are automatically created/renewed by the system versus which certificates must be manually created/renewed by the system administrator.
Platform certificates that are associated with optional platform components are only present if the optional platform component is configured (e.g. ). Platform certificates that are associated with Distributed Cloud are only present on SystemController systems or Subclouds.
| Certificate | Auto Created | Renewal Status |
|---|---|---|
| Etcd: | ||
| etcd Root CA certificate | Yes | NOT AUTO-RENEWED; Default expiry is set at 10 years |
| etcd server certificate | Yes | auto-renewed by cron job |
| etcd client certificate | Yes | auto-renewed by cron job |
| kube-apiserver's etcd client certificate | Yes | auto-renewed by cron job |
| Kubernetes: | ||
| Kubernetes Root CA Certificate | Yes | NOT AUTO-RENEWED; Default expiry is set at 10 years; MUST be renewed via CLI. |
| Cluster Admin client certificate used by kubectl | Yes | auto-renewed by cron job |
| kube-controller-manager client certificate | Yes | auto-renewed by cron job |
| kube-scheduler client certificate | Yes | auto-renewed by cron job |
| kube-apiserver server certificate | Yes | auto-renewed by cron job |
| kube-apiserver's kubelet client certificate | Yes | auto-renewed by cron job |
| kubelet client certificate | Yes | auto-renewed by kubelet. Feature enabled by default |
| front-proxy-client | Yes | front-proxy-client: auto-renewed by cron job |
| front-proxy-ca | Yes | front-proxy-ca: NOT AUTO-RENEWED; Default expiry is set at 10 years |
| system-local-ca | Yes | NOT AUTO-RENEWED. MUST be renewed via CLI |
| OpenLDAP Server Certificate | Yes | auto-renewed by system |
| StarlingX REST API & HORIZON Server Certificate | Yes (But the auto-created certificate is self-signed and should be changed) | auto-renewed if configured with cert-manager; NOT AUTO-RENEWED if
configured with system certificate-install .., must be renewed via
CLI |
| Local Registry Server Certificate | Yes (But the auto-created certificate is self-signed and should be changed) | auto-renewed if configured with cert-manager; NOT AUTO-RENEWED if
configured with system certificate-install .., must be renewed via
CLI |
| OIDC: | ||
| OIDC Client and Dex Server Server Certificate | No | auto-renewed if configured with cert-manager; NOT AUTO-RENEWED if configured with an externally generated certificate. MUST be renewed via CLI. |
| OIDC Client and Dex Server CA certificate | No | NOT AUTO-RENEWED. MUST be renewed via CLI. |
| OIDC Remote WAD CA Certificate | No | NOT AUTO-RENEWED. MUST be renewed via CLI. |
| Vault: | ||
| Vault Server Certificate | Yes | NOT AUTO-RENEWED; MUST be renewed via CLI. |
| Vault Root CA certificate | Yes | NOT AUTO-RENEWED; MUST be renewed via CLI. |
| Portieris: | ||
| Portieris Server Certificate | Yes | Auto renewed by cert-manager; BUT CUSTOMER MUST restart Portieris after the certificate is renewed |
| Portieris remote registry and notary server CA Certificate | No | NOT AUTO-RENEWED; CUSTOMER MUST renew via CLIs |
| DC Admin Endpoints: | ||
| Root CA DC Admin Endpoint CA Certificate | Yes | auto-renewed |
| Intermediate CA DC Admin Endpoint CA Certificate | Yes | auto-renewed |
| DC Admin Endpoint Server Certificate | Yes | auto-renewed |
| System trusted CA Certificates | No | NOT AUTO-RENEWED as these are certificates that are not necessarily owned by the platform |
Where:
- Auto created: the certificate is generated during system deployment or triggered by certain operations.
- Renewal Status: whether the certificate is renewed automatically by the system when expiry date approaches.
The specific certificates, and details such as expiration date, that
are present on a system can be displayed with a local script, sudo
show-certs.sh, see utility-script-to-display-certificates.
monitors the installed certificates on the system by raising alarms
for expired certificates and certificates that will expire soon, see
alarm-expiring-soon-and-expired-certificates-baf5b8f73009.
The following sections provide details on managing these certificates.
StarlingX REST API Applications and the Web Administration Server Certificate <starlingx-rest-api-applications-and-the-web-administration-server>Kubernetes Certificates <kubernetes-certificates-f4196d7cae9c>Local Registry Server Certificates <security-install-update-the-docker-registry-certificate>System Trusted CA Certificates <add-a-trusted-ca>
For further information about certificates expiration date or other
certificates information, see Display Certificates Installed on a System <utility-script-to-display-certificates>.
In addition, monitors the installed certificates on the system by
raising alarms for expire-soon certificates and for expired certificates
on the system, see Expiring-Soon and Expired Certificate Alarms
<alarm-expiring-soon-and-expired-certificates-baf5b8f73009>.