How to fix Floating IP Unavailable in Kubernetes

KubernetesBEGINNERMEDIUMUpdated Dec 6, 2025· 100 views

A floating IP unavailable error occurs in cloud providers (Vultr, DigitalOcean, Hetzner) when a reserved IP address cannot be assigned to a LoadBalancer service. This prevents external traffic from reaching the service, blocking ingress connectivity.

Quick fix

Fixes Floating IP Unavailable

# DigitalOcean:
digitalocean floating-ips list

# Vultr:
vultr reserved-ip list

# Hetzner Cloud:
hcloud floating-ip list

# Check account limits:
# - Login to web console
# - Check billing/quota section
# - Look for floating IP limits
  1. Check floating IP quota in cloud provider
  2. Verify cloud provider plugin is installed
  3. Check service configuration
  4. Check cloud credentials and permissions
kubernetes — error
# DigitalOcean:
digitalocean floating-ips list
# Vultr:
vultr reserved-ip list
# Hetzner Cloud:
hcloud floating-ip list
# Check account limits:
# - Login to web console
# - Check billing/quota section
# - Look for floating IP limits
Floating IP Unavailable

What this error means

Cloud providers offer floating IPs (elastic IPs, reserved IPs) that can be reassigned between instances. In Kubernetes LoadBalancer services, floating IPs are used to provide stable, public-facing IP addresses. When creating a LoadBalancer service, the cloud provider attempts to allocate a floating IP from your account's available pool. If the pool is exhausted or misconfigured, the allocation fails, leaving the service in "Pending" state.

Typical symptoms

  • kubectl get svc shows LoadBalancer service with <pending> EXTERNAL-IP
  • Service never acquires an external IP
  • Cloud provider console shows no new floating IP created
  • kubectl describe svc shows cloud provider error message
  • Events show "Failed to provision floating IP"
  • Logs show quota exceeded or allocation failure
  • Traffic cannot reach the service from outside cluster

Common causes

  1. Floating IP quota exceeded (account limit reached)
  2. Cloud provider plugin misconfigured or disabled
  3. Network or firewall blocking IP assignment
  4. Service annotation specifying unavailable IP
  5. Cloud credentials invalid or permissions missing
  6. Region/zone mismatch (IP in different region)
  7. Previous floating IP not released (orphaned)

How to fix "Floating IP Unavailable"

1Check floating IP quota in cloud provider

Verify you have available floating IPs:

bash
# DigitalOcean:
digitalocean floating-ips list

# Vultr:
vultr reserved-ip list

# Hetzner Cloud:
hcloud floating-ip list

# Check account limits:
# - Login to web console
# - Check billing/quota section
# - Look for floating IP limits

If quota is exhausted, release unused IPs or request increase.

2Verify cloud provider plugin is installed

Check the cloud controller manager:

bash
kubectl get pods -n kube-system | grep cloud-controller-manager
kubectl describe pod -n kube-system -l component=cloud-controller-manager

# Check logs:
kubectl logs -n kube-system -l component=cloud-controller-manager -f

# Verify it's configured:
kubectl get deploy -n kube-system -l component=cloud-controller-manager

If missing or not running, the service cannot allocate floating IPs.

3Check service configuration

Review the LoadBalancer service definition:

bash
kubectl get svc <service-name> -o yaml

# Look for:
apiVersion: v1
kind: Service
metadata:
  name: my-service
spec:
  type: LoadBalancer
  selector:
    app: my-app
  ports:
  - port: 80
    targetPort: 8080
  # Check for cloud-specific annotations:
  # annotations:
  #   service.beta.kubernetes.io/load-balancer-source-ranges: 0.0.0.0/0

Verify type is "LoadBalancer" and no conflicting annotations.

4Check cloud credentials and permissions

Ensure cloud provider credentials are valid:

bash
# Check secret with cloud credentials:
kubectl get secrets -n kube-system
kubectl describe secret -n kube-system cloud-provider-secret  # Name varies

# Verify credentials:
# DigitalOcean:
export DIGITALOCEAN_ACCESS_TOKEN=<token>
doctl auth init  # Verify token works

# Vultr:
export VULTR_API_KEY=<key>
vultr account info

# Hetzner:
export HCLOUD_TOKEN=<token>
hcloud project limits

If credentials are invalid, cloud operations will fail.

5Release orphaned floating IPs

Remove unused IPs to free quota:

bash
# List all floating IPs:
digitalocean floating-ips list

# Identify orphaned IPs (not attached to any droplet):
for ip in $(digitalocean floating-ips list --format IP); do
  status=$(digitalocean floating-ip get $ip --format Status)
  if [ "$status" == "new" ]; then
    echo "Orphaned: $ip"
    digitalocean floating-ip delete $ip  # Delete if safe
  fi
done

Orphaned IPs consume quota but serve no purpose.

6Manually assign floating IP via annotation

Pre-allocate and assign a specific floating IP:

bash
# Create floating IP manually:
digitalocean floating-ip reserve <region> --droplet-name <node>
# Returns: 192.0.2.1

# Assign to service via annotation:
kubectl annotate service <service-name> \
  service.beta.kubernetes.io/do-loadbalancer-ip=192.0.2.1

# Or in YAML:
apiVersion: v1
kind: Service
metadata:
  name: my-service
  annotations:
    service.beta.kubernetes.io/do-loadbalancer-ip: "192.0.2.1"
spec:
  type: LoadBalancer
  ...

Pre-allocating IP ensures availability.

7Check cloud provider logs

Debug cloud provider errors:

bash
# Check cloud controller manager logs:
kubectl logs -n kube-system -l component=cloud-controller-manager --tail=100

# Look for:
# - "floating-ip quota exceeded"
# - "failed to allocate IP"
# - "authentication failed"
# - API errors

# Check kubelet logs for service updates:
kubectl logs -n kube-system kubelet | grep -i loadbalancer

# Describe service for event messages:
kubectl describe svc <service-name>
# Look for "Events:" section

Logs reveal the exact failure reason.

8Monitor and request quota increase

Plan for growth and request higher limits:

bash
# Calculate current usage:
kubectl get svc --all-namespaces | grep LoadBalancer | wc -l

# Add 50% buffer for future growth
need_ips=$(( $(kubectl get svc -A | grep LoadBalancer | wc -l) * 2 ))
echo "Request quota: $need_ips floating IPs"

# For DigitalOcean, request increase via support ticket
# For Vultr, manage via account settings
# For Hetzner, use web console

Plan ahead for cluster growth.

Advanced notes

Floating IP quotas vary by cloud provider and account tier. DigitalOcean allows 3 free floating IPs per account. Vultr and Hetzner have similar limits. For large clusters with many services, pre-allocate floating IPs or upgrade to higher tier. Some providers support DNS instead of floating IPs (use Ingress with external DNS instead). Floating IP costs vary ($3-5/month typically). For high availability, use multiple LoadBalancer services with automatic failover. Consider using an Ingress controller (nginx, traefik) instead of multiple LoadBalancers to reduce floating IP usage. Monitor unused services and clean up to free quota. Document which services use floating IPs for capacity planning.

Frequently asked questions

What does "Floating IP Unavailable" mean?
Cloud providers offer floating IPs (elastic IPs, reserved IPs) that can be reassigned between instances. In Kubernetes LoadBalancer services, floating IPs are used to provide stable, public-facing IP addresses. When creating a LoadBalancer service, the cloud provider attempts to allocate a floating IP from your account's available pool.
How do I fix "Floating IP Unavailable"?
A floating IP unavailable error occurs in cloud providers (Vultr, DigitalOcean, Hetzner) when a reserved IP address cannot be assigned to a LoadBalancer service. This prevents external traffic from reaching the service, blocking ingress connectivity.
What causes "Floating IP Unavailable"?
Floating IP quota exceeded (account limit reached) Cloud provider plugin misconfigured or disabled Network or firewall blocking IP assignment
Is the "Floating IP Unavailable" error serious?
It is a medium-severity error — more of a blocker than a risk. The steps above resolve it.

Official resources & further reading