Several months ago, I started working on a Go linter (gomega-lint) for gomega. I’ve been using gomega at work for almost a year and love it now. I’ve formed some opinions on good practices for using gomega. But giving this kind of feedback during code reviews - it’s too late by that point.
You know that code that is tricky to unit test but easy to make an integration test for? And you track code coverage?
Well, the upcoming Go 1.20 release adds support for collecting code coverage from integration tests.
Go 1.20 has a new trick and can build binaries ready to collect coverage during integration tests.
In the same vein as the rest of my posts in the Container Networking series, I want to learn how Calico sets up pod routes between Kubernetes nodes.
If you log into a Kubernetes node using Calico and run ip route you’ll see something similar to:
Previously, I discussed how to Spin up a Ubuntu VM using Pulumi and libvirt. By the end, we had a fully working VM that we could SSH into with provided credentials for the Ubuntu user. But how could we begin to make this usable by others?
Pulumi is an Infrastructure as Code (IaC) tool that supports using Go, .Net, Python, and TypeScript/JavaScript. Libvirt is a tool for managing virtual machines (VM). Typically, teams use Pulumi with different cloud providers, but we can leverage libvirt to manage virtual machines on bare-metal servers, perfect for a homelab.