This is a clone of issue OCPBUGS-41824. The following is the description of the original issue:
—
Description of problem:
The kubeconfigs for the DNS Operator and the Ingress Operator are managed by Hypershift and they should only be managed by the cloud service provider. This can lead to the kubeconfig/certificate being invalid in the cases where the cloud service provider further manages the kubeconfig (for example ca-rotation).
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
- blocks
-
OCPBUGS-42992 Hypershift is managing kubeconfigs for DNS and Ingress operators
- Closed
- clones
-
OCPBUGS-41824 Hypershift is managing kubeconfigs for DNS and Ingress operators
- Verified
- is blocked by
-
OCPBUGS-42261 Hypershift is managing kubeconfigs for DNS and Ingress operators
- Closed
- is cloned by
-
OCPBUGS-42992 Hypershift is managing kubeconfigs for DNS and Ingress operators
- Closed
- links to
-
RHBA-2024:7944 OpenShift Container Platform 4.16.z bug fix update