The Limitations describe the following:
- There can only be one
LoadBalancer service per unique spec.ports[].port. Since floating IPs are transparent to Oxide instances, traffic will arrive on the instance’s internal IP address using spec.ports[].port. The service controller adds both the floating IP and the instance’s internal IP to the LoadBalancer status so that Kubernetes creates the per-node firewall rules needed to allow the traffic. Put another way, a load balancer configured to use port 443 will conflict with another load balancer configured to use port 443.
However, we could likely return an error when the user creates a LoadBalancer service with a port that's already in use. This will help in the floating IP implementation but it might not be desirable if we move the load balancer to use external subnets instead.
The Limitations describe the following:
However, we could likely return an error when the user creates a
LoadBalancerservice with a port that's already in use. This will help in the floating IP implementation but it might not be desirable if we move the load balancer to use external subnets instead.