Reservation and release of Loadbalancer IPs

less than a minute

Reserve floating IP addresses for the Loadbalancer is useful if you do not want them to change. This is realized through annotations in the service manifest, which is used to configure the load balancer.

Reservation of FloatingIPs

An annotation must be added to the service for the initial reservation of a FloatingIP.

metadata:
    annotations:
        loadbalancer.openstack.org/keep-floatingip: "true" # Reserves the FloatingIP in OpenStack

Further use of a FloatingIP

To use an already reserved floating IP, this must also be given to the new service.

metadata:
    annotations:
        loadbalancer.openstack.org/keep-floatingip: "true" # Reserves the FloatingIP in OpenStack
        loadbalancer.openstack.org/load-balancer-address: <FloatingIP> #  The corresponding FloatingIP is specified here
spec:
    loadBalancerIP: <FloatingIP> #  The corresponding floating IP is specified here

Release of FloatingIPs

The annotation loadbalancer.openstack.org/keep-floatingip: must be set to false. The service can then be deleted.

metadata:
    annotations:
        loadbalancer.openstack.org/keep-floatingip: "false" # Releases the FloatingIP in OpenStack
        loadbalancer.openstack.org/load-balancer-address: <FloatingIP> #  The corresponding FloatingIP is specified here
spec:
    loadBalancerIP: <FloatingIP> #  The corresponding floating IP is specified here

Release of FloatingIPs which are no longer known

If you don’t know which floating IPs you are currently using, you may open a support ticket in your customer panel.

Last modified 12.11.2024: Changing to new picture schema, removing aws docs, adding new screenshots (8887530)