RepoJournal
Kubernetes

@kubernetes

Container orchestration — what platform teams ship on

Pick a date

  1. Thu 21 may
  2. Sat 23 may
  3. Sun 24 may
  4. Mon 25 may
  5. Tue 26 may
  6. Wed 27 may
  7. Thu 28 may
  8. Fri 29 may
  9. Sat 30 may
  10. Sun 31 may
  11. Mon 1 jun
  12. Mon 8 jun
  13. Tue 9 jun
  14. Wed 10 jun
  15. Thu 11 jun
  16. Fri 12 jun
  17. Sat 13 jun
  18. Sun 14 jun
  19. Mon 15 jun
  20. Tue 16 jun
  21. Wed 17 jun
  22. Thu 18 jun
  23. Fri 19 jun
  24. Sat 27 jun
  25. Sun 28 jun
  26. Mon 29 jun
  27. Tue 30 jun
  28. Wed 1 jul
  29. Thu 2 jul
  30. Today 3 jul

The Wire · Showcase

KOPS HARDENS CCM SCHEDULING, DRA GPU DRIVER SHIPS v0.4.1

By RepoJournal · Filed · About Kubernetes

Cloud-controller-manager pods across five cloud providers now tolerate all node taints, eliminating a class of scheduling failures on heavily tainted control planes.

The kops project merged a critical change [1] that forces CCM pods to schedule regardless of node taint state by adding universal tolerations to AWS, Azure, DigitalOcean, GCP, and Scaleway deployments. This solves a real operational problem: when operators taint nodes to enforce workload isolation, the CCM itself could get stranded, breaking cloud resource management. In parallel, the DRA NVIDIA GPU driver [2] shipped v0.4.1 with verified multi-arch images and Helm charts promoted to the release registry [3]. The kops project also scaffolded an experimental roles feature flag [4] that adds placeholders for etcd, scheduler, CCM, and KCM as separate controllable components, setting up future multi-role capabilities without breaking existing deployments. On the dependency front, Azure provider maintainers enabled dependabot updates [5] by removing exclusions that were blocking security patches on cloud-provider-specific dependencies.

Action items

References

  1. [1] Make cloud-controller-manager pods tolerate all taints ↗ kubernetes/kops
  2. [2] Promoting dra-driver-nvidia-gpu image and helm chart for the release v0.4.1 ↗ kubernetes/k8s.io
  3. [3] Merge pull request #9666 from shivamerla/release_nvidia_driver_v0.4.1 kubernetes/k8s.io
  4. [4] Add an experimental roles feature flag. ↗ kubernetes/kops
  5. [5] Enable dependabot updates for the Azure provider ↗ kubernetes/autoscaler

FAQ

What changed in Kubernetes on June 30, 2026?
Cloud-controller-manager pods across five cloud providers now tolerate all node taints, eliminating a class of scheduling failures on heavily tainted control planes.
What should Kubernetes teams do about it?
Review kops CCM toleration change before next cluster upgrade if you run tainted control planes • Test experimental roles flag in kops if you manage multi-role control planes • Update DRA GPU driver to v0.4.1 if using NVIDIA GPU scheduling
Which Kubernetes repositories shipped on June 30, 2026?
kubernetes/kops, kubernetes/k8s.io, kubernetes/autoscaler

Related across the cluster

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.