Support LoadBalancerIP Field

[j0nr33v3]

Request to support LoadBalancerIP Field - so that LB is created with user specified IP (i.e. service will be exposed on same IP across service deletes and restarts)

https://kubernetes.io/docs/concepts/services-networking/service/#type-loadbalancer

Example

kind: Service
apiVersion: v1
metadata:
  name: my-service
spec:
  selector:
    app: MyApp
  ports:
  - protocol: TCP
    port: 80
    targetPort: 9376
  clusterIP: 10.0.171.239
  loadBalancerIP: 78.11.24.19
  type: LoadBalancer
status:
  loadBalancer:
    ingress:
    - ip: 146.148.47.155

[jhorwit2]

@j0nr33v3 this isn't possible until OCI allows us to set the IP of the load balancer.

[sneerin]

any updates on that? This breaks any work of services, templates, etc that relate to this setting?

[sneerin]

we got some clients caching and during some hard redeployments, sometimes we delete completely the service ( helm open issue), each time we do that, the IP updated, some DNS are not that fast up to 1h cache, that causing downtime for 1h. This issue means oracles clusters are not production-ready for us.

[andreshans]

is there any workaround suggested for this issue?

[b4dboi]

Hi @jhorwit2, I think there is a way how to set up a LoadBalancer in OCI using the concept of Reserved IPs. It is available even via API https://docs.oracle.com/en-us/iaas/api/#/en/networkloadbalancer/20200501/datatypes/CreateNetworkLoadBalancerDetails, search for reservedIps. I can imagine that the OCID of some pre-created Reserved IP could be a part of Load Balancer Annotations. The current state is really limiting for production deployments.