Hi all, I want to use the load balancer integration from Harvester in cluster integration. There is a dynamic IP pool option that you can define with selectors. This only protects against certain clusters in namespaces but the IP from the pool after isn't guaranteed. Can I limit the IP Pool usage to a specific namespace IN the guest cluster? I want to protect against issues of another service claiming that IP

Hi @great-cricket-28459 This exact use case is actually being tracked as a feature request in the Harvester repo and is currently in progress. In the meantime, there are a couple of workarounds listed in the issue thread that you can use. github.com/harvester/harvester/issues/4735

It seems to have been moved to the next version for quite some time. I only need one right now but it would be nice to have this in the future

If you need only one IP you can use the use the

/32

Harvester IP Pool trick and reference it explicitly via annotations on your service. This is also mentioned as a workaround in there. github.com/harvester/harvester/issues/4735#…

@late-van-32030 Downside of this is that this only works for 1 static IP. If you could atleast specify which pool you want to use than that would be enough. Then you can create multiple and call them. I will probably need more though

@great-cricket-28459 Yeah, you're right. there's no way to explicitly pick a pool from the LB side. it's purely scope-driven (network + project/namespace/guestCluster + priority), so it's "which pools serve this scope," not "choose your pool." So within one scope you effectively get one pool's worth of IPs, and you can't split services in the same namespace across multiple pools.