oracle / oracle/oci-cloud-controller-manager

CCM LoadBalancer - K8s service type LoadBalancer isn't enforcing `Spec.loadBalancerSourceRanges`

Open
#499 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
158
Forks
108
PR merge metrics
No merged PRs in 30d

Description

I am unable to make the loadBalancerSourceRanges work as I expected with the LoadBalancer controller. I have the following service:

---
apiVersion: v1
kind: Service
metadata:
  name: echoserver
  annotations:
    oci.oraclecloud.com/load-balancer-type: "nlb"
    oci.oraclecloud.com/ingress-ip-mode: "proxy"
    oci-network-load-balancer.oraclecloud.com/security-list-management-mode: "Frontend"
spec:
  selector:
    app: echoserver
  loadBalancerSourceRanges:
  - 10.0.0.0/24
  ports:
    - port: 80
      targetPort: 8080
      protocol: TCP
      name: http
    - port: 443
      targetPort: 8443
      protocol: TCP
      name: https
  type: LoadBalancer 

As this is a public load balancer I expected that setting the source range to 10.0.0.0/24 would prevent me from accessing the service over the public Internet from my source IP, but it does not - I can still access my echo-server.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Service manifest and trace the LoadBalancer controller entry point that processes loadBalancerSourceRanges and the OCI annotations. Reproduce the public access behavior described here, then inspect the resulting security rules. Done means traffic outside 10.0.0.0/24 is blocked for the public load balancer.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
cloud, infrastructure, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.