This document describes periodic maintenance that is required for your
Google Distributed Cloud clusters.

## Rotate certificate authorities

The certificate authorities (CAs) in a cluster are valid for ten years. For versions before 1.36.100,
the core cluster component `clientconfig-operator`, uses
a certificate that is valid for five years and is only renewed when you rotate
the cluster CA. To prevent this certificate from expiring, you must
[rotate your CAs](https://docs.cloud.google.com/kubernetes-engine/distributed-cloud/bare-metal/docs/how-to/ca-rotation.md.txt) at least once every five
years, even if you don't actively use external identity providers or
GKE Identity Service.

## Certificates for cluster components

Cluster components use certificates for authentication:

- **Control plane and node components** : Certificates for components including
  `kube-apiserver`, `kube-controller-manager`, `kube-scheduler`, `etcd`, and
  `kubelet` are valid for one year and are renewed during cluster
  [upgrade](https://docs.cloud.google.com/kubernetes-engine/distributed-cloud/bare-metal/docs/how-to/upgrade.md.txt). To prevent these certificates from
  expiring, you must upgrade your cluster at least once a year.

- **GKE Identity Service (`clientconfig-operator`)** : The certificate for
  the `clientconfig-operator` component is valid for ten years and is renewed
  when you [rotate certificate authorities](https://docs.cloud.google.com/kubernetes-engine/distributed-cloud/bare-metal/docs/how-to/ca-rotation.md.txt).

If the cluster certificates have expired, they must be
[renewed manually](https://docs.cloud.google.com/kubernetes-engine/distributed-cloud/bare-metal/docs/troubleshooting/expired-certs.md.txt). For more
information, see
[Certificate expiration](https://docs.cloud.google.com/kubernetes-engine/distributed-cloud/bare-metal/docs/troubleshooting/failure-mode-analysis.md.txt#certificate_expiration).