Skip to content

fix(aws/eks): align default Kubernetes version to 1.32 - #66

Merged
JLCode-tech merged 1 commit into
release/2.2from
fix/eks-k8s-1.32
Jun 29, 2026
Merged

JLCode-tech merged 1 commit into
release/2.2from
fix/eks-k8s-1.32

Conversation

@JLCode-tech

Copy link
Copy Markdown
Owner

Aligns external EKS module defaults to 1.32, matching the aws-k8s-foundation builtin blueprint and the bnk-forge-catalog-aws-eks blueprints. infra/aws/eks: kubernetes_version 1.30→1.32,
cluster_version 1.31→1.32; infra/aws/security: kubectl_version 1.30.0→1.32.0. Azure AKS (1.29) and ubuntu/kind (1.29.2) intentionally left — different platforms. Pairs with bnk-forge-v2 PR
fix/aws-k8s-foundation-k8s132.

Match the EKS k8s bump already in the aws-k8s-foundation builtin blueprint
and the bnk-forge-catalog-aws-eks blueprints (eks_cluster_version 1.32).
The infra/aws/eks module defaults lagged (kubernetes_version 1.30, the
redundant cluster_version 1.31) and the security module's kubectl_version
(1.30.0) is documented to track the EKS version. Bump all to 1.32 for
consistency across everything forge syncs.

Azure AKS (1.29) and ubuntu/kind (1.29.2) intentionally left — different
platforms with their own version-availability constraints.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@JLCode-tech
JLCode-tech merged commit 163e69a into release/2.2 Jun 29, 2026
2 checks passed
@JLCode-tech
JLCode-tech deleted the fix/eks-k8s-1.32 branch June 29, 2026 06:38
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