CuraDevOps

tag: Etcd · 7 items

Learn Kubernetes v1.37: etcd RangeStream graduates to beta, cuts API server memory on large reads
2026-09-02 · Kubernetes Blog · source ↗ #kubernetes#etcd#memory-optimization
  • Platform/SRE — Learn: RangeStream is still beta in v1.37 (requires etcd v3.7), so not yet production-adoptable, but SREs running clusters with many large objects (e.g., Pods at scale) should track this as a near-term mitigation for API server and etcd OOM risk during cache repopulation.
  • CI/CD — Skip
  • Leader — Skip
  • Signals: Kubernetes 1.37 EOL 2027-10-28 · etcd 3.7 supported
Plan archived etcd v3.7.1 patch release flagged with breaking change
2026-07-27 · Releases: etcd · source ↗ #etcd#kubernetes#breaking-change
  • Platform/SRE — Plan: etcd backs every Kubernetes control plane, and a breaking change in a patch release is unusual — review the v3.7.1 CHANGELOG and upgrade guide before applying this update to any cluster, and validate in a non-production environment first. No hard deadline exists, but the breaking-change flag makes this a planned, careful upgrade rather than routine patching.
  • CI/CD — Skip
  • Leader — Skip
  • Signals: breaking-change flagged
Plan archived etcd v3.6.14 patch release flagged with breaking change
2026-07-27 · Releases: etcd · source ↗ #etcd#kubernetes#breaking-change
  • Platform/SRE — Plan: etcd is the Kubernetes control plane’s backing store — a breaking-change flag in even a patch release means reviewing the upgrade guide before rolling this out to production clusters. No deadline is given, but operators should validate against their environment this quarter before routine patching.
  • CI/CD — Skip
  • Leader — Skip
  • Signals: breaking-change flagged
Plan archived etcd v3.5.33 patch release flags breaking change
2026-07-27 · Releases: etcd · source ↗ #etcd#kubernetes#patch-release
  • Platform/SRE — Plan: etcd backs every Kubernetes control plane, and a breaking-change flag on a patch release is unusual — review the CHANGELOG and upgrade guide before rolling this out to clusters; no hard deadline, but unreviewed breaking changes in a core datastore warrant a planned change window rather than routine rollout.
  • CI/CD — Skip
  • Leader — Skip
  • Signals: breaking-change flagged
Plan archived etcd v3.7.0 released with breaking changes
2026-07-13 · Releases: etcd · source ↗ #etcd#kubernetes#infrastructure
  • Platform/SRE — Plan: etcd is a critical Kubernetes control-plane component; v3.7.0 carries flagged breaking changes requiring review of the upgrade guide before any cluster upgrade. Plan the migration this quarter — no forced deadline in the signals, but breaking changes mean this needs a scoped project, not a routine bump.
  • CI/CD — Skip
  • Leader — Skip
  • Signals: breaking-change flagged
Plan archived etcd v3.7.0 released
2026-07-13 · Releases: etcd · source ↗ #etcd#kubernetes#infrastructure
  • Platform/SRE — Plan: etcd is the Kubernetes control-plane backing store, so any new minor release warrants a changelog review for deprecations, API changes, or breaking behavior before scheduling an upgrade cycle; no deadline or CVE signals are present to force earlier action.
  • CI/CD — Skip
  • Leader — Skip
Plan archived etcd v3.7.0 GA: RangeStream, v2store removal, protobuf overhaul
2026-07-10 · Kubernetes Blog · source ↗ #etcd#kubernetes#minor-release
  • Platform/SRE — Plan: etcd is the Kubernetes control-plane datastore, so this GA minor release is directly relevant; evaluate adopting v3.7 this quarter, particularly if large result-set latency or v2store remnants are pain points — no forced-upgrade deadline exists yet.
  • CI/CD — Skip
  • Leader — Skip
  • Signals: etcd 3.7 supported · etcd 3.6 supported