Commands icon
If icon
SlackIncomingWebhook icon
Schedule icon

Kubernetes CNI IPAM Node Pod Subnet Exhaustion Sentinel

Audits Kubernetes node allocatable pod capacity to detect CNI IPAM subnet exhaustion and prevent scheduling freezes.

Categories
CloudInfrastructure

How it works

This workflow inspects Kubernetes node allocatable pod limits (status.allocatable.pods) against running pods scheduled across each node. In cloud CNI implementations (such as AWS VPC CNI, Calico, or Azure CNI), each worker node is allocated a specific CIDR or secondary ENI IP pool. When pod densities approach node allocatable limits, CNI IP address management (IPAM) runs out of available IPs. If exhausted nodes are found, Slack is notified immediately.

What you get

  • Continuous monitoring of pod allocation density across worker nodes.
  • Prevents catastrophic FailedCreatePodSandBox scheduling deadlocks.
  • Early warning to provision additional node subnets or warm secondary ENIs.

Who it's for

  • Kubernetes Platform Engineers and Cloud Network Administrators.
  • SREs managing high-density microservice clusters on AWS EKS or GKE.

Why orchestrate this with Kestra

  • Cluster-Wide Assessment: Evaluates allocatable pod headroom across all nodes.
  • No Daemonset Required: Runs on-demand using official kubectl container images.
  • Proactive Scaling: Trigger cluster autoscaler node pool expansions before pods fail.

Prerequisites

  • Kubernetes cluster with read permissions on nodes and pods.
  • Secret SLACK_WEBHOOK configured in Kestra.

Quick start

  1. Import the blueprint.
  2. Configure threshold percentage (default 85%).
  3. Run the workflow to inspect node IPAM headroom.

How to extend

  • Query AWS VPC CNI custom resource ENIConfig or Calico IPPool directly.
  • Automate cordon and drain operations for nodes experiencing IP leaks.

Links

See How

New to Kestra?

Use blueprints to kickstart your first workflows.