Skip to content

2.1.8

Obsrv 2.1.8 release notes.

Release Date: 2026-06-25

Release Type: Minor

Objective: EKS upgrade from version 1.33 to 1.34, including control plane, addons, and node group.

Focus: EKS cluster version bump with updated addon versions and permanent node group version tracking via terraform.

Expected downtime: ~30 minutes (control plane + addons + rolling node replacement).

What’s New

Section titled “What’s New”
  • EKS 1.34 — Control plane, addons, and node group upgraded from 1.33 to 1.34.
  • Updated addons:
Addon1.33 version1.34 version
kube-proxyv1.33.0-eksbuild.2v1.34.6-eksbuild.13
vpc-cniv1.20.0-eksbuild.1v1.22.2-eksbuild.1
corednsv1.12.2-eksbuild.4v1.13.2-eksbuild.11

Migration Steps

Section titled “Migration Steps”

1. Plan and apply

Section titled “1. Plan and apply”

This step upgrades the control plane first, then addons, then triggers rolling node replacement — terraform handles the order automatically.

Terminal window
cd obsrv-automation/terraform/aws


terraform plan  -var-file=vars/cluster_overrides.tfvars -target=module.eks
terraform apply -var-file=vars/cluster_overrides.tfvars -target=module.eks

Apply order (terraform handles this automatically):

  1. EKS control plane → ~5 min
  2. Addons → ~2 min
  3. Node group rolling replacement → ~8-10 min per node

2. Monitor node rollout

Section titled “2. Monitor node rollout”

Each node is drained and replaced one at a time. Watch node status until all show the new version before proceeding to verify.

Terminal window
watch -n 10 'kubectl get nodes -o wide'

3. Verify

Section titled “3. Verify”
Terminal window
# Nodes — all must show v1.34.x
kubectl get nodes -o jsonpath='{range .items[*]}{.metadata.name}{"\t"}{.status.nodeInfo.kubeletVersion}{"\n"}{end}'


# No broken pods
kubectl get pods -A | grep -Ev "Running|Completed"