Skip to content

K8SPXC-1784 Updated the info about updating default rotation policy for cert-manager #310

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
nastena1606 wants to merge 2 commits into
base: main
Choose a base branch
from
+17 −23
Open

K8SPXC-1784 Updated the info about updating default rotation policy for cert-manager #310

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bdd67e9
Updated the info about updating default rotation policy for cert-manager
nastena1606 May 4, 2026
ef2a576
Potential fix for pull request finding
nastena1606 May 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
40 changes: 17 additions & 23 deletions docs/tls-cert-manager.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,41 +22,35 @@ by the same CA (Certificate authority).
Self-signed issuer allows you to deploy and use the Percona
Operator without creating a cluster issuer separately.



## Install the *cert-manager*

The cert-manager requires its own namespace
The cert-manager requires its own namespace.

The steps to install the *cert-manager* are the following:

1. Create the `cert-manager` namespace:
1. Run the following command to install the cert-manager:

```bash
kubectl create namespace cert-manager
kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v{{ certmanagerversion }}/cert-manager.yaml
```

2. Disable resource validations on the `cert-manager` namespace:

```bash
kubectl label namespace cert-manager certmanager.k8s.io/disable-validation=true
```
This creates the dedicated namespace `cert-manager` and installs cert-manager Deployments, Pods and Services in this namespace. It also creates cluster-wide resources such as Custom Resource Definitions and RBAC to enable the use of cert-manager in any namespace in the Kubernetes cluster.

3. Install the cert-manager:
2. Update the default rotation policy to not rotate the private key Secret associated with a Certificate object automatically upon the certificate reissue.

```bash
kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v{{ certmanagerversion }}/cert-manager.yaml
```
=== "For cert-manager v1.19.2 and above"

4. For cert-manager v1.18.0 and above, update the default rotation policy to not rotate the private key Secret associated with a Certificate object automatically upon the certificate reissue:

```bash
kubectl patch certificate cluster1-ca-cert --type=merge -p '{"spec":{"privateKey":{"rotationPolicy":"Never"}}}'
```
The default rotation policy is set to "Never" by default. No action is needed from your side.

=== "For cert-manager v1.18.0 - v1.19.1"

Run the following command **after you have deployed the Operator and created the database cluster**, because the `cluster1-ca-cert` Certificate is created by the Operator during cluster creation and does not exist during cert-manager installation:

```bash
kubectl patch certificate cluster1-ca-cert --type=merge -p '{"spec":{"privateKey":{"rotationPolicy":"Never"}}}'
```

This workaround ensures the correct start of the database cluster upon the certificate renewal.
This workaround ensures the correct start of the database cluster upon the certificate renewal.

5. Verify the *cert-manager* by running the following command:
3. Verify the *cert-manager* by running the following command:

```bash
kubectl get pods -n cert-manager
Expand Down