Cordon a Kubernetes node and evict pods while respecting disruption budgets.
npx skills add https://github.com/X-McKay/kubani --skill drain-node
Please help me install this Agent Skill. Skill: drain-node Source: https://github.com/X-McKay/kubani/tree/main/kubani/skills/k8s/remediation/drain-node Command: npx skills add https://github.com/X-McKay/kubani --skill drain-node
This Skill safely removes all running pods from a Kubernetes node, preparing it for maintenance or decommissioning without disrupting critical services.
Use the drain-node skill to safely evict pods from the node named 'worker-node-3'.
High-intent search queries and answers about installing and using this skill.
Safely draining a Kubernetes node involves cordoning the node to prevent new scheduling and gracefully evicting existing pods, allowing them to reschedule elsewhere while respecting pod disruption budgets and ignoring DaemonSet pods.
Cordoning a node marks it as unschedulable, preventing the Kubernetes scheduler from placing any new pods onto the target node while existing pods are being gracefully evicted.
Yes, an MCP server integration is required for Kubernetes API interactions to safely cordon the target node and evict pods through the automated remediation process.
No, the pod eviction process ignores DaemonSet pods. DaemonSets are designed to run on every node, so they are intentionally left untouched during the node draining process.
Pod eviction respects pod disruption budgets to guarantee a minimum number of available pod replicas remain running during the node drain, preventing critical application outages during maintenance.
X-McKayAssess Kubernetes cluster health by checking node readiness, system pods, and events.
bnaylorAutomate rolling upgrades for HA MicroK8s clusters via SSH with stateful recovery.
iulianditaRun read-only Kubernetes cluster health checks and generate status reports.
keiretsu-labsDiagnose Kubernetes pod failures with kubectl commands in the openclaw namespace.
