kubernetes
Increase default max-shared-lb from 2
/kind feature
What happened:
It is possible to share a LoadBalancer between multiple Kubernetes services: https://github.com/kubernetes/cloud-provider-openstack/blob/master/docs/openstack-cloud-controller-manager/expose-applications-using-loadbalancer-type-service.md#sharing-load-balancer-with-multiple-services
But the default setting of max-shared-lb is only 2, so you can only have 2 Kubernetes services that share a LoadBalancer. This makes it useful, but very limited.
If there is a good reason for the default to be this low it would be great for it to be documented.
What you expected to happen:
To be able to create more than 2 services that share a LoadBalancer without having to convince my Kubernetes provider to change the setting from the default
How to reproduce it:
- Create a Service with Kind=LoadBalancer
- Create a second Service that shares the
loadbalancer.openstack.org/load-balancer-address&loadbalancer.openstack.org/load-balancer-idannotations but uses different ports. - Observe this succeeds
- Create a third Service that shares the
loadbalancer.openstack.org/load-balancer-address&loadbalancer.openstack.org/load-balancer-idannotations but uses different ports. - Observe this gives the error message:
load balancer NAME already shared with 2 Services
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
