How to fix Floating IP Unavailable in Kubernetes

# 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

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

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

# 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

# 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

# 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
  ...

# 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

# 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