Deep Dive: Long Term Support WG
summary
Community survey gets 334 completed survey responses out of ~600 starters and shows roughly a third to half of clusters running unsupported versions while about half of respondents prefer slower minor-release cadence. Findings push two concrete models: monthly releases with stabilization month that forks an LTS branch, or a slower sequential-upgrade path usable today. Pain points are test-matrix growth, dependency churn (Go and transitive libs), and weak conformance coverage; recommendations focus on stronger CI, expanded conformance tests, and evaluating seamless in-place upgrade vs immutable-host rollout (requires one extra node).
AI-written summary · about
chapters (13)
- 0:00Start
- 1:10What is WG LTS
- 2:29What LTS
- 3:56Possible benefits of LTS
- 5:39Possible risks, costs of LTS
- 6:16Survey: What do you want?
- 8:23Survey: Who is "you"?
- 9:31Survey: What is run?
- 13:22Survey: What problems?
- 14:11Survey: What support is desired?
- 15:43Upgrade Cadence Options
- 20:09Discussion
- 29:09Survey: When do you upgrade?
related talks
29mKubernetes WG-LTS: Why We Need LTS?
52mViability of Kubernetes community LTS
36mDeep Dive: SIG Release
37mBringing LTS To Kubernetes: Lessons From the Field
35mUnderstanding the Future of Ingress-nginx
23mA little less testing, a little more quality
22mKeynote: Backstage with Kubernetes
18mKubernetes Project Update