Skip to content

k8sServiceHost multiple IPs/Hosts #19038

Open
@schmitch

Description

Proposal / RFE

Is your feature request related to a problem?
no, it's just a inconvenience on bare-metal

Describe the solution you'd like
currently we run multiple clusters with cilium and use the kube-proxy'less mode and one thing is always not that good in our bare metal clusters is specifiyng the k8sServiceHost. This is especially a problem when a node needs to get rebooted.
We would prefer if it would be possible to have that load balanced or retried with multiple addresses.

Something like:

k8sMasterServices:
  - host: 10.10.30.11
     port: 6443 # somehow github formats that incorrectly?
  - host: 10.10.30.12
     port: 6443
  - host: 10.10.30.13
     port: 6443

this would make it much more easy to use the kube-proxy less mode when running on bare-metal since an external load balancer would not be needed, especially when running with something like k3s where the master's do load balancer internally.

(btw. at the moment we use kube-vip for that, but preferably we would drop it, once k8s is up and running you can use metallb and announce the kube-api masters by using a endpoint and svc and feed that to metallb)

Metadata

Assignees

Labels

area/loadbalancingImpacts load-balancing and Kubernetes service implementationskind/featureThis introduces new functionality.pinnedThese issues are not marked stale by our issue bot.sig/datapathImpacts bpf/ or low-level forwarding details, including map management and monitor messages.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions