176 wires and counting

$ follow Kubernetes

Keep up with Kubernetes in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-11-01
stories 138

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

kops stops pruning Karpenter NodePools it cannot fully render

By RepoJournal · Filed · About Kubernetes · Composed from the cited sources · methodology

kops fixed a partial-update path where `kops-channels` pruned Karpenter NodePools and subnet tags for instance groups that were not in the render, causing Karpenter to terminate nodes it should have kept.

aws: Keep Karpenter NodePools when updating only some instance groups kubernetes/kops

by hakman

A partial update (`kops update cluster --instance-group` or `--instance-group-roles`, or the first step of `kops reconcile cluster`) renders the karpenter.sh addon with only the NodePools and EC2NodeClasses of the groups being updated, and kops-channels then pruned the ones missing from that manifest. The addon now copies the other Karpenter objects through instead, so a single-group update no ...

Tag the subnets for all Karpenter instance groups kubernetes/kops

by Ciprian Hacman

The companion fix for the same partial-update path: an EC2NodeClass selects subnets by the tag `kops.k8s.io/instance-group/<name>`, and only the updated groups' subnets were tagged, with missing tags never added to existing subnets. Subnets now get tagged for all Karpenter instance groups.

channels: prune APIService, IngressClass and CSIDriver objects kubernetes/kops

by hakman

`channels` prunes addon objects by a hardcoded GroupKind list that had fallen behind the manifests, so an object of an unlisted kind was never removed when dropped from a manifest and the only signal was a warning. `APIService` (spotinst-kubernetes-cluster-controller), `IngressClass` (aws-load-balancer-controller) and `CSIDriver` (storage) are now swept.

stage kops/kubernetes to s3 buckets when running ec2 jobs kubernetes/kops

by upodroid

The EC2 CI path now stages kops and Kubernetes artifacts to S3 buckets before running its jobs, merged as the ec2-build-fix branch.

Lint on macOS 27 kubernetes/minikube

by nirs

Quieter elsewhere: minikube added linting on a macOS 27 runner and reformatted test.yaml, bumped kube-vip from v1.3.0 to v1.3.1 for multi-control-plane HA, kong/kubernetes-ingress-controller from 3.5.13 to 3.5.14, and hugo from v0.168.0 to v0.169.0 on the site.

Quick answers

What shipped in Kubernetes on November 1, 2026?
kops fixed a partial-update path where `kops-channels` pruned Karpenter NodePools and subnet tags for instance groups that were not in the render, causing Karpenter to terminate nodes it should have kept. In total, 87 commits and 51 pull requests landed.
Who contributed to Kubernetes on November 1, 2026?
6 developers shipped this update, including themoriarti, upodroid, hakman, kubernetes-prow[bot], nirs, and Kubernetes Publisher.
What were the notable Kubernetes updates?
aws: Keep Karpenter NodePools when updating only some instance groups, Tag the subnets for all Karpenter instance groups, and channels: prune APIService, IngressClass and CSIDriver objects.