Canonical’s support for Kubernetes 1.6.2 released

Marco Ceppi

Marco Ceppi

on 4 May 2017

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!

Ubuntu cloud

Ubuntu offers all the training, software infrastructure, tools, services and support you need for your public and private clouds.

Sign up for email updates

Choose the topics you're interested in

 

Related posts

Decreasing the complexity of IoT adoption with Edge as a Service model

  Last week, much of the IoT industry descended on Santa Clara, California, for the annual IoT World trade show. One of the exhibitors present were Rigado who Canonical partnered with earlier this year to deploy Ubuntu Core on their…

Canonical Managed Cloud adds data protection and recovery with Trilio

Canonical BootStack and Ubuntu Advantage customers now can access TrilioVault OpenStack Vancouver: – May 22, 2018 – Canonical and Trilio announced today a partnership agreement to deliver TrilioVault backup and recovery…

Ubuntu Server development summary – 22 May 2018

Hello Ubuntu Server The purpose of this communication is to provide a status update and highlights for any interesting subjects from the Ubuntu Server Team. If you would like to reach the server team, you can find us at the #ubuntu-server…