-
Bug
-
Resolution: Done-Errata
-
Undefined
-
4.15, 4.16.0
This is a clone of issue OCPBUGS-30119. The following is the description of the original issue:
—
Description of problem:
`ensureSigningCertKeyPair` and `ensureTargetCertKeyPair` are always updating secret type. if the secret requires metadata update, its previous content will not be retained
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Install 4.6 cluster (or make sure installer-generated secrets have `type: SecretTypeTLS` instead of `type: kubernetes.io/tls` 2. Run secret sync 3. Check secret contents
Actual results:
Secret was regenerated with new content
Expected results:
Existing content should be preserved, content is not modified
Additional info:
This causes api-int CA update for clusters born in 4.6 or earlier.
- clones
-
OCPBUGS-30119 cert-syncer is forcibly changing secret type without retaining content
- Closed
- is blocked by
-
OCPBUGS-30119 cert-syncer is forcibly changing secret type without retaining content
- Closed
- is related to
-
OCPBUGS-31384 api-int Certificate Authority rotation during 4.14.17 to 4.15.3 update
- Closed
- links to
-
RHSA-2024:1210 OpenShift Container Platform 4.15.z security update