oracle / oracle/oci-cloud-controller-manager
OCI-CCM is not setting the ProviderID as per CCM Spec
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 158
- Forks
- 108
- PR merge metrics
- No merged PRs in 30d
Description
If I understand it correctly the OCI CCM is not setting the ProviderID on the nodes, but requiring the --provider-id flag to be set on the kubelet. This responsibility was move from the kubelet to the CCM ages ago: https://kubernetes.io/docs/concepts/architecture/cloud-controller/#functions-of-the-ccm
Especially in combination with ClusterAPI the ProviderID is usually not known when the configuration of a node is set, as the configuration needs to be passed to the cloud-init section when creating the instance. As the CCM is running as a DaemonSet, why can't it just fetch the ProviderID using IDMS for it's own node?
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 by tracing how the OCI CCM DaemonSet handles its own node and how the kubelet currently receives --provider-id. Read the Kubernetes CCM specification and investigate fetching the node's ProviderID through IDMS, especially for ClusterAPI-created nodes. Done means the CCM sets ProviderID without requiring kubelet configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100