oracle / oracle/oci-cloud-controller-manager
CCM config `loadBalancer.securityListManagementMode` ignored
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 158
- Forks
- 108
- PR merge metrics
- No merged PRs in 30d
Description
I am having an issue with the CCM LB Controller. Out of the possible values for the cloud-provider.yaml, loadBalancer.securityListManagementMode, the controller always reads None:
2025-06-05T15:14:03.894Z INFO oci/load_balancer_security_lists.go:95 Security list management mode: "None". Not managing security lists. {"component": "cloud-controller-manager"}
2025-06-05T15:14:03.895Z WARN oci/util.go:175 oke resource tracking system tags are not present in cloud-config.yaml {"component": "cloud-controller-manager", "loadBalancerName": "********-test/echoserver/2fa3eb61-6507-47a0-a4d7-6b3ac132f4ca", "serviceName": "echoserver", "loadBalancerType": "nlb", "serviceUid": "2fa3eb61-6507-47a0-a4d7-6b3ac132f4ca", "loadBalancerID": "ocid1.networkloadbalancer.oc1.iad..ddyq", "loadBalancerType": "nlb"}
If I set it to an invalid value, the LBC crashes (as expected):
F0605 15:13:01.878708 1 main.go:82] Cloud provider could not be initialized: could not init cloud provider "oci": loadBalancer.securityListManagementMode: Invalid value: "Donkey": invalid security list management mode
So I know it's reading my config secret properly.
Is there anything that would cause it not manage any of the security groups even though we set loadBalancer.securityListManagementMode: Frontend? The LoadBalancer is created ok but there is no security group attached so it doesn't pass traffic.
Note that if i add the annotation oci-network-load-balancer.oraclecloud.com/security-list-management-mode: "Frontend" I see in the CCM logs that this recognised for this specific instance of the LB, and the LB now passes traffic. However the OCI console for the LB still doesn't show any LB.
Should it be possible to set the default securityListManagementMode via the CCM config?
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
Read oci/load_balancer_security_lists.go around line 95 and trace how cloud-provider.yaml's loadBalancer.securityListManagementMode is passed into the controller; compare it with the per-service annotation path described here. Done means a configured Frontend default is honored without an annotation and the resulting load balancer receives the expected security list.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cloud, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100