Your submission was sent successfully! Close

You have successfully unsubscribed! Close

Thank you for signing up for our newsletter!
In these regular emails you will find the latest updates about Ubuntu and upcoming events where you can meet our team.Close

Canonical Distribution of Kubernetes: Development Summary- August 24


on 24 August 2017

This article was last updated 4 years ago.

This article originally appeared on Tim Van Steenburgh’s blog

August 18th concluded our most recent development sprint on the Canonical Distribution of Kubernetes (CDK). Here are some highlights:

  • CI failures fixed. We spent some time fixing a handful of CI failures that had crept in recently. We’re back to green now and looking good for a patch release of CDK in the near future.
  • Canal charm implemented. Canal provides an alternative to Flannel for those who need network policy support on CDK. We have more testing to do on Canal in this and the next sprint, but for those wishing to kick the tires, you can take Canal for a test drive with: juju deploy cs:~cynerva/canonical-kubernetes-canal-0 (NB: doesn’t work on LXD). In the current sprint we’ll be adding the Canal charm and bundle to CI for more thorough and regular testing.
  • RBAC support. We updated our default cluster add-ons and microbot example to work with RBAC, completing our RBAC proof-of-concept work. In the current sprint we’re getting CI updated with more tests for RBAC.
  • s390x support. We looked into getting upstream s390x builds for heapster (success!) and ingress (no success). For ingress we hit an impasse with a QEMU bug, so in the interest of continuing to make forward progress, we plan to build this image on actual s390x hardware for now. In the current sprint we’ll be building that image and then running e2e tests on s390x to see where we’re at!

Finally, in case you missed it, be sure to check out the new features coming to conjure-up — a tool for deploying CDK on any public cloud, private cloud, or developer laptop. The latest edge build of conjure-up includes automatic native-cloud integration for CDK on AWS, and the introduction of Add-ons, which can deploy software (like Deis, for example) onto your new Kubernetes cluster in a repeatable and automated way.

If you’d like to follow along more closely with CDK development, you can do so in the following places:

To quickly get started with deploying Canonical Kubernetes click the deploy button below.


Until next time!

kubernetes logo

What is Kubernetes?

Kubernetes, or K8s for short, is an open source platform pioneered by Google, which started as a simple container orchestration tool but has grown into a platform for deploying, monitoring and managing apps and services across clouds.

Learn more about Kubernetes ›

Newsletter signup

Get the latest Ubuntu news and updates in your inbox.

By submitting this form, I confirm that I have read and agree to Canonical's Privacy Policy.

Related posts

How should a great K8s distro feel? Try the new Canonical Kubernetes, now in beta

Try the new Canonical Kubernetes beta, our new distribution that combines ZeroOps for small clusters and intelligent automation for larger production...

Canonical Kubernetes 1.29 is now generally available

A new upstream Kubernetes release, 1.29, is generally available, with significant new features and bugfixes. Canonical closely follows upstream development,...

How to use Ubuntu in GKE on nodes and in containers

Google Kubernetes Engine (GKE) traces its roots back to Google’s development of Borg in 2004, a Google internal system managing clusters and applications. In...