You may have noticed an uptick in the rate at which we have been cutting releases of Kubernetes over the last week. I'll give a brief overview of the recent releases and why we cut them. We hope to avoid having so many releases in close proximity in the future.
- This release was exactly the same as v1.3.0 with the above mentioned security issue fixed
- This release also tested our ability to cut a single change release without pulling in all of the other changes on the release branch (if you look closely, we created a
release-1.3.0 branch last week)
- Fixed a
P0 issue discovered in when running Kubernetes in GCE
- Also rolled up the security fix and other changes that were on the 1.3 release branch
v1.3.3 (expected Thursday, July 21st)
- Rollup build from the 1.3 branch fixing another
P0 issue running Kubernetes on GCE and
multiple fixes for large clusters
- There were many approved cherry picks that didn't have cherry pick PRs yet which will be in the next patch release
v1.3.4 (expected next week)
- Targeted for a number of visible storage issues
We are working on improving our test infrastructure to avoid finding P0 bugs *after* cutting a minor release. However, we do expect to occasionally cut extra patch releases as security issues as they are discovered.
Please feel free to reach out (publicly or privately) if you have any questions or concerns.