// Module included in the following assemblies:
//
// assembly-security.adoc

[id='proc-renewing-ca-certs-manually-{context}']

= Manually renewing the CA certificates generated by the Cluster Operator

Cluster and clients CA certificates generated by the Cluster Operator auto-renew at the start of their respective certificate renewal periods.
However, you can use the `strimzi.io/force-renew` annotation to manually renew one or both of these certificates before the certificate renewal period starts.
You might do this for security reasons, or if you have xref:con-certificate-renewal-str[changed the renewal or validity periods for the certificates].

A renewed certificate uses the same private key as the old certificate.

NOTE: If you are using your own CA certificates, the `force-renew` annotation cannot be used.
Instead, follow the procedure for xref:renewing-your-own-ca-certificates-{context}[renewing your own CA certificates].

.Prerequisites

* The Cluster Operator is running.
* A Kafka cluster in which CA certificates and private keys are installed.

.Procedure

. Apply the `strimzi.io/force-renew` annotation to the `Secret` that contains the CA certificate that you want to renew.
+
.Annotation for the Secret that forces renewal of certificates
[cols="3*",options="header",stripes="none",separator=¦]
|===

¦Certificate
¦Secret
¦Annotate command

¦Cluster CA
¦_KAFKA-CLUSTER-NAME_-cluster-ca-cert
m¦kubectl annotate secret _KAFKA-CLUSTER-NAME_-cluster-ca-cert strimzi.io/force-renew=true

¦Clients CA
¦_KAFKA-CLUSTER-NAME_-clients-ca-cert
m¦kubectl annotate secret _KAFKA-CLUSTER-NAME_-clients-ca-cert strimzi.io/force-renew=true

|===
+
At the next reconciliation the Cluster Operator will generate a new CA certificate for the `Secret` that you annotated.
If maintenance time windows are configured, the Cluster Operator will generate the new CA certificate at the first reconciliation within the next maintenance time window.
+
Client applications must reload the cluster and clients CA certificates that were renewed by the Cluster Operator.

. Check the period the CA certificate is valid:
+
For example, using an `openssl` command:
+
[source,shell,subs="+quotes"]
kubectl get secret _CA-CERTIFICATE-SECRET_ -o 'jsonpath={.data._CA-CERTIFICATE_}' | base64 -d | openssl x509 -subject -issuer -startdate -enddate -noout
+
_CA-CERTIFICATE-SECRET_ is the name of the `Secret`, which is `_KAFKA-CLUSTER-NAME_-cluster-ca-cert` for the cluster CA certificate and `_KAFKA-CLUSTER-NAME_-clients-ca-cert` for the clients CA certificate.
+
_CA-CERTIFICATE_ is the name of the CA certificate, such as `jsonpath={.data.ca\.crt}`.
+
The command returns a `notBefore` and `notAfter` date, which is the validity period for the CA certificate.
+
For example, for a cluster CA certificate:
+
[source,shell,subs="+quotes"]
----
subject=O = io.strimzi, CN = cluster-ca v0
issuer=O = io.strimzi, CN = cluster-ca v0
notBefore=Jun 30 09:43:54 2020 GMT
notAfter=Jun 30 09:43:54 2021 GMT
----

. Delete old certificates from the Secret.
+
When components are using the new certificates, older certificates might still be active.
Delete the old certificates to remove any potential security risk.

[role="_additional-resources"]
.Additional resources

* xref:certificates-and-secrets-str[]
* xref:assembly-maintenance-time-windows-str[]
* link:{BookURLConfiguring}#type-CertificateAuthority-reference[`CertificateAuthority` schema reference^]
