Part 3 - Automating Multi-Arch Builds Using Github Actions This is Part 3 of a series on building out multi-arch services in Kubernetes using Golang. I highly recommend reading Part 1 and Part 2 prior to working through this entry. The first two will provide you with the background on how to build a multi-arch container using Go whereas this one concerns automating the build process. For this guide there is also a supplementary Github repository containing the working example code, it can be found here github.
Part 2 - Building CGO for Multi Arch This is Part 2 of a series on building out multi-arch services in Kubernetes using Golang. For a guide on how to build plain Go services in multiple architectures see Part 1 of this series. In this post we’ll be building containers similar to the previous example with the added feature of supporting CGO.
If you’ve read any of Rob Pike’s writings on the design of Go, watched one of his talks online, or attended a conference where he’s spoken you’ll know that Rob firmly believes that CGO is not Go.
Part 1 - Building Multi-arch Containers This is Part 1 of a series that’s going to take you through the concept of a heterogenous Kubernetes cluster supporting multiple different CPU architectures. It will be primarily focused on using Go since that’s my currently favorite language and might be one of the easiest languages to use that supports multi-arch. In this series we’re going to cover building Go containers for multi-arch, how to secure these containers against intrusion, benefits and tradeoffs of different container configurations, creating a build system that can generate multiple architectures, and finally deploying a hardware agnostic service to Kubernetes.
