Skip to main content

Your submission was sent successfully! Close

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

Thank you for contacting our team. We will be in touch shortly.Close

  1. Blog
  2. Article

Canonical
on 10 August 2017

Canonical Distribution of Kubernetes: Dev Summary 2017 (Week 32)


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

Testing & Planning

  • CDK offline testing plan. We wrote up a plan for testing CDK in an environment where there is no (or severely limited) egress internet access. The end goal is to ensure that CDK can be deployed in this scenario, and create docs describing how to do it. Initial testing begins in the current sprint.
  • etcd2-to-etcd3 migration plan. We wrote up a plan for upgrading existing CDK clusters from etcd2 to etcd3 if desired, and making etcd3 the new default. While the plan is in place, we don’t have any implementation work planned in the current sprint.
  • Canal. We wrote up a design doc for implementing Canal (Calico-on-Flannel) for CDK. Implementation of the Canal charm was scheduled for the current sprint and is currently in code review.
  • We added a Jenkins job to test our stable charms against the latest upstream patch release. A passing build here tells us that we can release the latest binaries for CDK without breaking currently-deployed clusters.

Features

  • Completed RBAC proof-of-concept work. At this point we know how to turn RBAC on/off via charm config, and what changes are needed in CDK to make this work. In the coming weeks we’ll be working on moving from proof-of-concept to production-ready.
  • s390x support. We started by snapping the major cluster components. There are some docker images that don’t have s390x builds, namely nginx-ingress-controller, heapster-grafana, and addon-resizer. We’ll be following up on these in the current sprint.
  • Calico. We updated the Calico CNI charm to use the latest Calico binaries, and added the Calico charm and bundles to CI.

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

Until next time!

This was originally featured on Tim Van Steenburgh’s blog

Related posts


Gokhan Cetinkaya
30 September 2024

How to deploy AI workloads at the edge using open source solutions

AI Partners

Running AI workloads at the edge with Canonical and Lenovo AI is driving a new wave of opportunities in all kinds of edge settings—from predictive maintenance in manufacturing, to virtual assistants in healthcare, to telco router optimisation in the most remote locations. But to support these AI workloads running virtually everywhere, com ...


Cedric Gegout
30 September 2024

The waiting game is over. 5G is coming to the edge.

Telecommunications Article

Canonical and Omdia’s report reveals that 96% of CSPs will launch commercial 5G edge computing within 2 years. In this blog, we examine the drivers behind this optimism. ...


Stephanie Domas
30 September 2024

What the Cyber Resilience Act (CRA) means for IoT manufacturers

Compliance Hardening

The EU Cyber Resilience Act has considerable repercussions for the IoT device manufacturers. In this blog, we explore these new regulatory requirements and give our blueprint for compliant, market-ready devices. ...