--- title: Announcing The Canonical Distribution of Kubernetes 1.5.1 description: We’re proud to announce support for 1.5.1 in the Canonical Distribution of Kubernetes. This is a pure upstream distribution of Kubernetes, designed to be easily deployable to public clouds, on-premise, bare metal, and developer laptops. Kubernetes 1.5.1 includes a ton of new features and bugfixes, and we encourage you to check out the rel […] url: https://canonical.com/blog/announcing-canonical-kubernetes-1-5-1?format=md --- 1. [Blog](https://canonical.com/blog) 2. Article --- [Jorge O. Castro](https://canonical.com/blog/author/jorge "More about Jorge O. Castro") 16 December 2016 # Announcing The Canonical Distribution of Kubernetes 1.5.1 [Charmed Kubernetes](https://canonical.com/blog/tag/charmed-kubernetes) [kubernetes](https://canonical.com/blog/tag/kubernetes) --- Share the article We’re proud to announce support for 1.5.1 in the Canonical Distribution of Kubernetes. This is a pure upstream distribution of Kubernetes, designed to be easily deployable to public clouds, on-premise, bare metal, and developer laptops. Kubernetes 1.5.1 includes a ton of new features and bugfixes, and we encourage you to [check out the release notes](http://blog.kubernetes.io/2016/12/kubernetes-1.5-supporting-production-workloads.html). ## Getting Started: Here’s the simplest way to get a Kubernetes 1.5.1 cluster up and running on an Ubuntu 16.04 system: ``` sudo apt-add-repository ppa:juju/stable sudo apt-add-repository ppa:conjure-up/next sudo apt update sudo apt install conjure-up conjure-up kubernetes ``` During the installation conjure-up will ask you what cloud you want to deploy on and prompt you for the proper credentials. If you’re deploying to local containers (LXD) see [these instructions](https://kubernetes.io/docs/getting-started-guides/ubuntu/local/) for localhost-specific considerations. For production grade deployments and cluster lifecycle management it is recommended to read the [full Canonical Distribution of Kubernetes documentation.](https://github.com/castrojo/kubernetes.github.io/blob/ubuntu-lifecycle-revisions/docs/getting-started-guides/ubuntu/) Home page: Source code: ## New features * Full support for Kubernetes v1.5.1. * The charms now support the Container Network Interface (CNI). + The changes to the [flannel integration](https://jujucharms.com/u/containers/flannel/) are incompatible with the old method, as a result you must redeploy your cluster to get the latest release. + Flannel is now CNI only. The SDN plugin interface has been removed. + CNI support will allow us to support other CNI based Software Defined Network (SDN) applications, such as Calico and Weave. * In order to provide a more pure upstream Kubernetes experience, and support the wide range of amazing integration work being done by the community, the Elastic Stack is no longer included by default. Deploying and integrating with the Elastic Stack is still supported and is provided as a post deployment option. * Added debug actions to the kubernetes-master and kubernetes-worker charms. See the debugging section below. ## General Fixes * [#94](https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/94)SDN Plugin relationship not properly cleaning states on remove-relation * [#121](https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/121)Use the ginkgo resource in the e2e layer * [#122](https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/122)DNS may not be available during kubedns-relation causing failures * [#124](https://github.com/juju-solutions/bundle-canonical-kubernetes/pull/124) DNS may not be available during kubedns-relation causing failures * [#126](https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/126) etcd backup * [#127](https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/127) persistent ESB volume for etcd * [#130](https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/130) Addons are not upgraded during charm upgrades * [#136](https://github.com/juju-solutions/bundle-canonical-kubernetes/pull/136) Test improvements, and bumping versions of master and worker. * Juju 2.0 instruction update fixes #128 * [#147](https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/147) Need to integrate better in the testgrid * [#149](https://github.com/juju-solutions/bundle-canonical-kubernetes/pull/149) Include containers logs in the collection by filebeat so docker images spilling info to its stdout will be collected too * [#150](https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/150) Update for 1.5.0 - needs new flag 'anonymous-auth' * [#155](https://github.com/juju-solutions/bundle-canonical-kubernetes/pull/155) remove references to the elastic stack from the docs * [#156](https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/156) Update the local.yaml with the CNI release * [#157](https://github.com/juju-solutions/bundle-canonical-kubernetes/pull/157) update local.yaml * [#158](https://github.com/juju-solutions/bundle-canonical-kubernetes/pull/158) Bump revision of kubernetes-master ## Etcd layer-specific changes * [#61](https://github.com/juju-solutions/layer-etcd/pull/61) Adds the restore action * [#38](https://github.com/juju-solutions/layer-etcd/issues/38) Timeout Error during automated testing * [#46](https://github.com/juju-solutions/layer-etcd/issues/46) The openssl configuration code is broken * [#50](https://github.com/juju-solutions/layer-etcd/issues/50) layer-etcd needs to integrate with an CA instead of performing the CA operations itself * [#58](https://github.com/juju-solutions/layer-etcd/issues/58) Add snapshot/restore actions * [#59](https://github.com/juju-solutions/layer-etcd/pull/59) Adds the snapshot action * [#60](https://github.com/juju-solutions/layer-etcd/pull/60) Strip out the (leader) status message appender * [#45](https://github.com/juju-solutions/layer-etcd/issues/45) The etcd charm pulls easy-rsa from github.com * [#62](https://github.com/juju-solutions/layer-etcd/pull/62) Fixed lint error * [#63](https://github.com/juju-solutions/layer-etcd/pull/63) Adds initial persistent external storage support * [#64](https://github.com/juju-solutions/layer-etcd/pull/64) Fixing the source with the new flake8 rules. * [#65](https://github.com/juju-solutions/layer-etcd/pull/65) Layer tls-client rework * [#67](https://github.com/juju-solutions/layer-etcd/pull/67) Fixes for #66 * [#68](https://github.com/juju-solutions/layer-etcd/issues/68) Update the readme with current action names * [#69](https://github.com/juju-solutions/layer-etcd/pull/69) Rename non-existant action to the proper package-client-credentials action ## Docker layer-specific changes: * [#54](https://github.com/juju-solutions/layer-docker/issues/54) Updating the charm state from events inside containers * [#96](https://github.com/juju-solutions/layer-docker/pull/96) Add support for dockerhost * [#97](https://github.com/juju-solutions/layer-docker/pull/97) Add debug script to layer-docker ## Unfiled/un-scheduled fixes: * Adds addon tactic to generate addon manifests from template in the repository at build time * Fix for addons racing to deploy before kube-dns is ready * Adds warning message when service-cidr is changed (immutable option) * Added code docstrings improved ## Debugging To use a debug action on master: `juju run-action kubernetes-master/0 debug` To use a debug action on a worker: `juju run-action kubernetes-worker/0 debug` Example: `juju run-action kubernetes-master/0 debug` Will run the debugging command and return an action id: `Action queued with id: eb1c95dc-fe05-4e2e-8824-fb5d985f475e` You can then query the action output which includes the debug output and instructions on how to download the data: `juju show-action-output eb1c95dc-fe05-4e2e-8824-fb5d985f475e` `results:  command: juju scp kubernetes-master/0:/home/ubuntu/debug-20161216153022.tar.gz .  path: /home/ubuntu/debug-20161216153022.tar.gz status: completed` The above commands will execute several debug scripts on the unit. It produces a tree with the following information: * charm-unitdata * docker images, version, ps, info * filesystem information * inotify * juju-logs * All kubectl and cluster information * Kubernetes-master-services * Kubernetes-worker-services * Network Information * Package Information * Systemd logs and dumps. This feature is also encapsulated via the framework in [layer-debug](https://github.com/charms/layer-debug). This means you can easily, consistently, and efficiently add your own debugging routines. Consider submitting useful ones to us! ## How to contact us: We're normally found in these Slack channels and attend these sig meetings regularly: * [Sig-cluster-lifecycle](https://kubernetes.slack.com/messages/sig-cluster-lifecycle/) * [sig-cluster-ops](https://kubernetes.slack.com/messages/sig-cluster-ops/) We also monitor the Kubernetes mailing lists and other [community channels](http://kubernetes.io/community/), feel free to reach out to us. As always, PRs, recommendations, and bug reports are welcome: . We hope you enjoy this release as much as we enjoyed bringing it to you! ## Sign up for our newsletter Get the latest Canonical news and updates in your inbox. Work email: \*I agree to receive information about Canonical's products and services. By submitting this form, I confirm that I have read and agree to [Canonical's Privacy Policy](https://canonical.com/legal/dataprivacy). Sign up ## Share on --- ## Related posts [### How to set up a micro lab: four principles for a reliable homelab](https://canonical.com/blog/how-to-set-up-a-reliable-homelab) After over a decade of running a homelab, I have learned a few difficult lessons. Although it begins as a “lab,” you inevitably end up with something you want to keep. If a... [Jake Nabasny](https://canonical.com/blog/author/slapcat) 17 March 2026 [### Deploy your Spring Boot application to production](https://canonical.com/blog/deploy-spring-application-to-production) In this article we walk through the steps required to deploy a Spring Boot application to production using Juju and Kubernetes. The goal is to showcase the integration of the... [Javier de la Puente](https://canonical.com/blog/author/javierdelapuente) 13 January 2026 [### Harnessing the potential of 5G with Kubernetes: a cloud-native telco transformation perspective](https://canonical.com/blog/harnessing-the-potential-of-5g-with-kubernetes-a-cloud-native-telco-transformation-perspective) Telecommunications networks are undergoing a cloud-native revolution. 5G promises ultra-fast connectivity and real-time services, but achieving those benefits requires an... [Benjamin Ryzman](https://canonical.com/blog/author/benjaminryzman) 10 December 2025 [### Canonical releases FIPS-enabled Kubernetes](https://canonical.com/blog/canonical-releases-fips-enabled-kubernetes) Today at KubeCon North America, Canonical, the publisher of Ubuntu, released support to enable FIPS mode in its Kubernetes distribution, providing everything needed to create... [Canonical](https://canonical.com/blog/author/canonical) 11 November 2025