CCM should have a "Backend" mode for oci-load-balancer-security-list-management-mode

Is this a BUG REPORT or FEATURE REQUEST?

FEATURE REQUEST

Choose one: BUG REPORT or FEATURE REQUEST

I'd like to have a loadbalancer with whitelisted ingress IPs. This is not currently possible with CCM without choosing oci-load-balancer-security-list-management-mode = "None", which leaves me to manage the egress rules on the LB security lists. If I choose oci-load-balancer-security-list-management-mode = "All" or "Frontend", CCM adds a 0.0.0.0/0 ingress rule which overrides any IP whitelist I may have set up. Instead, I'd like the ability to pick oci-load-balancer-security-list-management-mode = "Backend", where CCM manages the egress rules, but not the ingress rules.

Versions

CCM Version:

Environment:

• Kubernetes version (use kubectl version):
• OS (e.g. from /etc/os-release):
• Kernel (e.g. uname -a):
• Others:

What happened?

What you expected to happen?

How to reproduce it (as minimally and precisely as possible)?

Anything else we need to know?

Start by locating the CCM handling for oci-load-balancer-security-list-management-mode and the code that manages load balancer security-list rules. Verify how the existing None, All, and Frontend modes behave, then define the Backend mode so egress rules are managed without adding ingress rules. Confirm completion with a load balancer that retains a whitelisted ingress configuration.