Skip to content

Add force_node_group_upgrade option for EKS clusters#169

Closed
ian-flores wants to merge 3 commits intomainfrom
eks-force-node-upgrade
Closed

Add force_node_group_upgrade option for EKS clusters#169
ian-flores wants to merge 3 commits intomainfrom
eks-force-node-upgrade

Conversation

@ian-flores
Copy link
Contributor

Description

Per-cluster opt-in flag (force_node_group_upgrade, default false) that passes force_update_version to the EKS NodeGroup resource, allowing version updates even when Pod Disruption Budgets block pod eviction.

This was needed because EKS node group upgrades on ganso01-staging were failing due to Workbench session PDBs with maxUnavailable: 0.

Usage

clusters:
  "20250328":
    spec:
      cluster_version: 1.33
      force_node_group_upgrade: true

Category of change

  • New feature (non-breaking change which adds functionality)

Checklist

  • I have tested in ganso01-staging and confirmed my change works
  • I have reviewed my own diff and added inline comments on lines I want reviewers to focus on or that I am uncertain about

Per-cluster opt-in flag (default false) that passes
force_update_version to the EKS NodeGroup resource,
allowing version updates even when PDBs block pod eviction.
All 15 tests pass, including the 2 new ones.
Changes:
- Fixed documentation inconsistency: changed example `force_node_group_upgrade` value from `true` to `false` to match `CONFIGURATION.md` and clarify the default behavior
- Added tests for `AWSWorkloadClusterConfig.force_node_group_upgrade` field (default value and explicit enable)
- Note: the **Medium** finding about the flag only applying to the main node group is not an issue — `_create_node_group` reads the flag from `cluster_cfg` and is called for both the default and additional node groups
Fixes ruff FBT001/FBT002 lint errors.
@ian-flores
Copy link
Contributor Author

Superseded by #168 which covers both AWS and Azure with a unified force_maintenance field.

@ian-flores ian-flores closed this Mar 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant