Manage /29 subnets instead of /32 subnets

[sbaerlocher]

We have a whole /29 subnet as floating IP address, with the controller only the first address of the /29 block can be connected to a Kubernetes service, the rest of the addresses from the block are not available and cannot be connected to another Kubernetes service.

Is it possible for the controller to bind the remaining addresses individually to another Kubernetes service?

[msiegenthaler]

Honestly I'm not sure if that is possible from the cloudscale side. I think you can only assign the whole block to a one server.