Skip to main content

NodeGroup Safety Protections

Comprehensive safety mechanisms prevent accidental cluster disruption.

Protection Overview

Multiple protection layers ensure cluster stability:

  • Last NodeGroup Protection: Prevents deletion of final NodeGroup
  • Master NodeGroup Protection: Prevents control plane NodeGroup deletion
  • Status-Based Protection: Only allows deletion of NodeGroups in safe states
  • Role-Based Protection: Restricts deletion to worker NodeGroups only
  • User Confirmation: Requires explicit confirmation for deletions

Protection Rules

1. Cannot Delete Last NodeGroup

Rule: Cannot delete the last remaining NodeGroup in a cluster

Purpose:

  • Ensures cluster maintains compute capacity
  • Prevents accidental removal of all worker nodes
  • Maintains ability to run applications

Implementation:

  • Real-time counting of active NodeGroups
  • Delete button automatically disabled for last NodeGroup
  • Visual indication shows why deletion is prevented
  • Applies regardless of NodeGroup role or status

2. Master NodeGroup Protection

Rule: Cannot delete NodeGroups with "master" or "control-plane" role

Purpose:

  • Master nodes run essential Kubernetes components
  • Control plane cannot be removed while cluster exists
  • Prevents cluster from becoming non-functional

Implementation:

  • System identifies NodeGroups by assigned role
  • Delete button completely hidden for master NodeGroups
  • Cannot be overridden or bypassed
  • Master NodeGroups managed automatically by service

3. Status-Based Protection

Rule: Can only delete NodeGroups with "Ready" status

Protected Statuses:

StatusReasonProtection Duration
CreatingNodeGroup creation in progressUntil creation completes
ScalingNodes being added/removedUntil scaling completes
UpdatingConfiguration being changedUntil update completes
ErrorNodeGroup has encountered errorsUntil errors resolved

Safe Status:

  • Ready: NodeGroup is operational and stable
  • All functions available: Create, scale, delete operations possible
  • No ongoing operations affecting NodeGroup

4. Worker NodeGroup Only Deletion

Rule: Only worker NodeGroups can be deleted

Implementation:

  • System verifies NodeGroup role before allowing deletion
  • Only worker NodeGroups show delete buttons
  • Master NodeGroups completely protected from deletion
  • UI clearly distinguishes between NodeGroup types