squidpickles

Multiplatform (amd64 and arm) Kubernetes cluster setup

The official guide for setting up Kubernetes using kubeadm works well for clusters of one architecture. But, the main problem that crops up is the kube-proxy image defaults to the architecture of the master node (where kubeadm was run in the first place).

This causes issues when arm nodes join the cluster, as they will try to execute the amd64 version of kube-proxy, and will fail.

It turns out that the pod running kube-proxy is configured using a DaemonSet. With a small edit to the configuration, it's possible to create multiple DaemonSets—one for each architecture.

Steps

Follow the instructions at https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/ for setting up the master node. I've been using Weave Net as the network plugin; it see

squidpickles

uscan and uupdate howto

Post by cjstm » Tue Mar 31, 2009 1:06 am

So you have ampache-3.4.4-0ubuntu1 installed and you want to give 3.5x a try, but wait 3.5 is not in the archives yet? Or better yet, you have PHP-5.2.6-0ubuntu1 installed and a newer version of PHP has come out and you want it now and not 6 months from now when the next release of Ubuntu comes out. Well the nice people at Debian/Ubuntu have developed a couple of tools to help you out. uscan and uupdate, which are part of the devscripts package, will help you update ANY Ubuntu/Debian package that has a watch file.

The first thing we need to do is install some needed packages.

squidpickles

Keybase proof

I hereby claim:

• I am squidpickles on github.
• I am sweetpea (https://keybase.io/sweetpea) on keybase.
• I have a public key whose fingerprint is C58B C742 F387 ED7F 126C 7FAB E3FD 5B99 8F8E 9F23

To claim this, I am signing this object: