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 SHIPS APISERVER-ONLY NODES, KUBE-OPENAPI FIXES STDLIB JSON COLLISION

By RepoJournal · Filed · About Kubernetes

Kops now lets you run dedicated API server nodes separate from control plane workers, solving a years-old load balancer problem that sent traffic to both when you only wanted one.

Kops landed three related changes that reshape how you can distribute control plane work across nodes [1] [2] [3]. The issue: when you had both APIServer and Control Plane nodes, the load balancer sent traffic to both, forcing your core controllers to share resources with API traffic. Now with the new --api-server-size flag and DNS None routing, traffic routes only to APIServer nodes, protecting controller capacity. This is the topology you've been asking for. Over in kube-openapi, a critical fix landed to insulate go-json-experiment from stdlib JSON packages [4] [5]. Without this, Go 1.27's changing json/v2 prerelease behavior was causing unit test failures. The fix drops aliases to json/v1 and json/v2, ensuring go-json-experiment stays self-contained until the actual stdlib migration. Test-infra cleaned up benchmark noise by removing yaml, table, and json-pretty LIST benchmark jobs [6], keeping only JSON, proto, and cbor for cleaner signal on scalability regressions. Kops also hardened RHEL 10+ support by loading the ip_set kernel module and disabling firewalld on ForceNftables distros [7], unblocking Calico e2e failures across the grid.

Action items

References

  1. [1] API only CLI ↗ kubernetes/kops
  2. [2] Fixing LB behavior when you have both APIServer and Control Plane. kubernetes/kops
  3. [3] Adding flag to enable machine type for APIServer only. kubernetes/kops
  4. [4] Insulate go-json-experiment from stdlib ↗ kubernetes/kube-openapi
  5. [5] Merge pull request #616 from liggitt/insulate-stdlib kubernetes/kube-openapi
  6. [6] Remove yaml, table, and json-pretty LIST benchmark jobs ↗ kubernetes/test-infra
  7. [7] nodeup: load ip_set module and disable firewalld on RHEL10 ↗ kubernetes/kops

FAQ

What changed in Kubernetes on June 19, 2026?
Kops now lets you run dedicated API server nodes separate from control plane workers, solving a years-old load balancer problem that sent traffic to both when you only wanted one.
What should Kubernetes teams do about it?
Review kops 1.35+ release notes if you run dedicated APIServer topology - new --api-server-size flag is live • Merge kube-openapi stdlib insulation fix into your vendored version before upgrading Go toolchain past 1.27 • Monitor test-infra benchmark job consolidation if you have custom scalability test configs
Which Kubernetes repositories shipped on June 19, 2026?
kubernetes/kops, kubernetes/kube-openapi, kubernetes/test-infra

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.