-
Bug
-
Resolution: Done-Errata
-
Normal
-
4.15.0
-
None
-
No
-
False
-
-
-
Bug Fix
-
In Progress
Description of problem:
The way CCM is deployed, it gets the kubeconfig configuration from the environment it runs on, which is the Management cluster. Thus, it communicates with the Kubernetes Api Server (KAS) of the Management Cluster (MC) instead of the KAS of the Hosted Cluster it is part of.
Version-Release number of selected component (if applicable):
4.15.0
How reproducible:
100%
Steps to Reproduce:
1. Deploy a hosted cluster 2. oc debug to the node running the HC CCM 3. crictl ps -a to list all the containers 4. crictl inspect X # Where X is the container id of the CCM container 5. nsenter -n -t pid_of_ccm_container 6. tcpdump
Actual results:
Communication goes to MC KAS
Expected results:
Communication goes to HC KAS
Additional info:
- blocks
-
OCPBUGS-23936 CCM uses MC's KAS instead of HC's KAS
- Closed
- is cloned by
-
OCPBUGS-23936 CCM uses MC's KAS instead of HC's KAS
- Closed
- is triggered by
-
HOSTEDCP-1282 Investigate if we need KAS access label in cloud controller manager
- Closed
- links to
-
RHEA-2023:7198 rpm
- mentioned on
(1 mentioned on)