oracle / oracle/oci-cloud-controller-manager
Deployment stuck due to nodeSelector.node-role.kubernetes.io/control-plane value
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 158
- Forks
- 108
- PR merge metrics
- No merged PRs in 30d
Description
I encountered this issue while deploying both CCM and CSI.
In the CCM manifest:
spec:
nodeSelector:
node-role.kubernetes.io/control-plane: ""
Similarly, in the CSI controller manifest:
spec:
nodeSelector:
node-role.kubernetes.io/control-plane: ""
In my cluster, control-plane nodes have the label:
node-role.kubernetes.io/control-plane: "true"
which caused both CCM and CSI controllers to not find any nodes. After patching their node selectors to be:
spec:
nodeSelector:
node-role.kubernetes.io/control-plane: "true"
everything worked right away.
How can I get CCM and CSI to work without having to patch them?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with manifests/cloud-controller-manager/oci-cloud-controller-manager.yaml and manifests/container-storage-interface/oci-csi-controller-driver.yaml, focusing on the nodeSelector entries linked in the report. Deploy both manifests in a cluster whose control-plane nodes use the reported label value and verify that the CCM and CSI controllers are scheduled successfully without manual patching.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100