Canonical’s support for Kubernetes 1.6.2 released

Tags:

We’re proud to announce support for Kubernetes 1.6.2 in the Canonical Distribution of Kubernetes and the Kubernetes Charms. This is a pure upstream distribution of Kubernetes, built with operators in mind. It allows operators do deploy, manage, and operate Kubernetes on public clouds, on-premise (ie vSphere, OpenStack), bare metal, and developer laptops. Kubernetes 1.6.2 is a patch release comprised of mostly bugfixes.

Getting Started

Here’s the simplest way to get a Kubernetes 1.6.2 cluster up and running:

# linux
 sudo snap install conjure-up --classic
 conjure-up kubernetes

# macOS
 brew 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 for localhost-specific considerations.

For production grade deployments and cluster lifecycle management it is recommended to read the full Canonical Distribution of Kubernetes documentation.

How to upgrade

To upgrade an existing 1.5.x or 1.6.x cluster, follow the upgrade instructions in the docs. Following these instructions will upgrade the charm code and resources to the Kubernetes 1.6.2 release of the charms.

New Features

  • Support for Kubernetes v1.6.2.
  • Update kubernetes-e2e charm to use snaps – pr:45044
  • Add namespace-{list, create, delete} actions to the kubernetes-master layer – pr:44277
  • Add cifs-utils package to kubernetes-worker (required for Azure) – pr:45117, fixes:227
  • Document NodePort networking for CDK – pr:44863, fixes:259

Bug Fixes

  • Update outdated link in kubernetes-master readme – pr:44988
  • Faster juju status updates when charm config changes – pr:44959, fixes:263
  • Make new leader retrieve certs from old leader – pr:43620, fixes:43563
  • Append authentication tokens instead of overwriting – pr:43620, fixes:43519
  • Ensure kubernetes-worker juju layer registry action uses correct ingress controller option name – pr:44921, fixes:44920
  • Send dns details only after cdk-addons are configured – pr:44945, fixes:40386, fixes:262
  • Fix ceph-secret type to kubernetes.io/rbd – pr:44635
  • When multiple masters, make worker choose one at random instead of trying to use all – pr:44677, fixes:255
  • Prevent installation of upstream (possibly unsupported by k8s) docker – pr:44681
  • Add –delete-local-data option to pause action – pr:44391, fixes:44392
  • Handle etcd scale events properly – pr:44967, fixes:43461
  • Resolve juju vsphere hostname bug showing only a single node in a scaled node-pool – pr:44780, fixes:237

How to contact us

We’re normally found in these Slack channels and attend these sig meetings regularly:

Or via email: kuberentes@ubuntu.com

Operators are an important part of Kubernetes, we encourage you to participate with other members of the Kubernetes community!

We also monitor the Kubernetes mailing lists and other community channels, feel free to reach out to us. As always, PRs, recommendations, and bug reports are welcome!

Newsletter signup

Select topics you’re
interested in

In submitting this form, I confirm that I have read and agree to Canonical’s Privacy Notice and Privacy Policy.

Related posts

We are changing the way you build snaps from GitHub repos

On the 11th March 2020 we introduced a new process for building a snap using GitHub repos to snapcraft.io. Here is all you need to know about this update....

GNOME 3.34 snapcraft extension

We constantly strive to empower developers. Part of that aim extends to making development easier, for example improving build tools and documentation. As an...

An adventure through the Snap Store

An application store with a large number of entries is a double-edged sword. It’s often a good sign of a vibrant, thriving community of software creators,...