This article describes how easy it is for users of Charmed Kubernetes to switch from the Docker container runtime to containerd. You may have heard that Kubernetes is deprecating Docker as a container runtime after v1.20. Docker as an underlying runtime is being deprecated in favor of runtimes that use the Container Runtime Interface(CRI) created for Kubernetes, such as containerd.

Ubuntu and Launchpad use OpenPGP keys heavily. Each source package is signed with the uploader’s key, and binary and source package downloads from Ubuntu’s primary archives and from users’ Personal Package Archives (PPAs) are indirectly signed by the publisher process with per-archive keys of its own. Access to Launchpad’s bug-manipulation interface is also controlled by OpenPGP. As a result, Launchpad needs a reliable key-storage and synchronization mechanism.

OpenStack, the cloud computing platform, has proved to be a beacon of success for open source. It rounds off 10 years in existence this year, a period which has seen it reach nearly 200 countries, and we want to look ahead to what the future holds for the technology.

Today, we’re excited to announce that EKS is available outside of AWS, on any Ubuntu system, with the EKS snap. This announcement builds on the existing collaboration between Amazon and Canonical to ensure the quality, security, and usability of Ubuntu-based EKS clusters on AWS. “Amazon EKS Distro (EKS-D) builds on our productive collaboration with Canonical around Ubuntu on AWS, and allows us to expand EKS beyond AWS cloud on any machine running Ubuntu.

A Linux kernel for each developer team, which uses it to bring up target boards. Bespoke, built, issued, and maintained over years by the vendor. Teams that focus on building great apps, rather than figuring out hardware dependencies. Happy developers that bootstrap smart devices in no time. This is what highly productive embedded systems development should look like. Let’s unpack that vision.

November 24th 2020: Canonical has published the LTS Docker Image Portfolio, a curated set of secure container application images, on Docker Hub. The LTS Docker Image Portfolio comes with up to ten years Extended Security Maintenance by Canonical. “LTS Images are built on trusted infrastructure, in a secure environment, with guarantees of stable security updates,” said Mark Lewis, VP Application Services at Canonical.

Kubernetes and robotics make a great match. However, as we have seen, robots running ROS 2 can be tricky to set up on Kubernetes. This blog series has explored running ROS 2 on Kubernetes, set up a simple talker and listener, and distributed that demo across three machines. The configurations presented may not quite fit your implementation, and you may want to dig a bit deeper into network traffic when troubleshooting.

Our simple ROS 2 talker and listener setup runs well on a single Kubernetes node, now let’s distribute it out across multiple computers. This article builds upon our simple ROS 2 talker / listener setup by running it on multiple K8s nodes. At the completion of this setup expect to have a ROS2 Kubernetes cluster running MicroK8s on three different machines. Applying a single configuration file distributes the ROS 2 workload across the machines.