oracle / oracle/oci-cloud-controller-manager
CCM still allocating fixed shape load balancers by default
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 158
- Forks
- 108
- PR merge metrics
- No merged PRs in 30d
Description
Is this a BUG REPORT or FEATURE REQUEST?
Choose one: BUG REPORT
Versions
CCM Version: No clue, using OKE
Environment:
- Kubernetes version (use
kubectl version): 1.25.4 - OS (e.g. from /etc/os-release): Oracle Linux 8
- Kernel (e.g.
uname -a): whatever gets provisioned with OKE - Others:
What happened?
When I install an ingress controller or do anything that creates a Server of type LoadBalancer, it is provisioning a fixed shape load balancer.
What you expected to happen?
I expect CCM to coordinate with other OCI teams to make sure that the cloud services are working as expected.
How to reproduce it (as minimally and precisely as possible)?
Create an OKE cluster, install an ingress controller like nginx or traefik, and go look at the Load Balancer created.
Anything else we need to know?
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 reproducing this on an OKE cluster with Kubernetes 1.25.4: install an ingress controller such as nginx or traefik and inspect the resulting LoadBalancer. Trace how CCM handles a Service of type LoadBalancer and identify where the default fixed shape is selected. Done means newly created load balancers use the current supported shape behavior rather than the retired fixed shape.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100