The Canonical Distribution of Kubernetes: Development Summary #3
Last Friday, one week after the Kubernetes 1.7 release, we released version 1.7 of the Canonical Distribution of Kubernetes (CDK). That release coincided with the end of our latest two-week development sprint.
Everything we did in that sprint contributed to the release in some way. We fixed some bugs. Merged a final feature. Updated some docs. But mostly, we tested. We wrote new test cases. We ran 1.7 deployments on multiple clouds. We ran upgrades from 1.6 to 1.7 on those clouds. We ran scaling tests. We ran the upstream end-to-end tests.
The team is putting tons of effort into our testing setup right now, and it’s paying off. With version 1.7, CDK is more rock-solid than ever! Dependability, pure upstream binaries, incredible ease-of-deployment on any cloud, and quick, painless upgrades…what’s not to love? :-)
We’re really excited about test automation for CDK right now, but it’s not just for the sake of dependability. It’s for the freedom to move fast. To deliver more of the features that make CDK the easiest-to-deploy-and-operate Kubernetes distribution out there, and to deliver them quickly and with high confidence.
If you’d like to follow along more closely with CDK development, you can do so in the following places:
- https://github.com/kubernetes/kubernetes (cluster/juju directory)
- Kubernetes Slack channels and SIG meetings
- #juju on Freenode IRC
- email@example.com mailing list
Until next time!