oracle / oracle/oci-cloud-controller-manager
Provide an annotation to disable appending private NLB IP address to service external IPs
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: FEATURE REQUEST
When creating a Service of type LoadBalancer it's ExternalIPs value will be used by components such as external-dns to create A records for traffic routing, however, as the private internal IPv4 address of the NLB is appended to the Ingress IPs property of the LoadBalancerStatus returned to service and both the public IPv4 and private IPv4 are added to DNS.
It would be helpful to disable this functionality when external-dns, or other components which reference this property and expect only public IP addresses are deployed.
https://github.com/kubernetes-sigs/external-dns/issues/2810 - Issue discussing this in external-dns
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 cloud controller manager populates the Kubernetes Service LoadBalancerStatus Ingress IPs for a LoadBalancer backed by an NLB. Define how an annotation should be read and verify that it suppresses the private NLB address while retaining public addresses, including coverage for external-dns-style consumers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- cloud, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100