Stian’s blog.
Gateway API for dummies
I recently had a use-case where I could finally tinker with Gateway API, a new interface for handling service traffic in Kubernetes. You can think of it as a successor to the current Ingress APIs. Gateway API is built and maintained by the Kubernetes Network Special Interest Group. What is Gateway API? # Gateway API is essentially just an API, it is a set of CRDs that you install in your cluster and does not come with a controller of any kind. A separate Gateway Controller has to be installed for things to work, there are many implementations to choose from but some examples include Envoy Gateway, Traefik Proxy, Cilium and Istio.
Configuring clients to use a container registry mirror
This is part two in a series of blog posts about container registry mirrors. The previous post focused on setting up a mirror in Kubernetes, now we will look at how to configure various clients to use it. Note
How to set up a simple registry mirror in Kubernetes
For the longest time I held off on setting up a container registry mirror because I assumed I would have to set up a potentially maintenance heavy solution like Harbor, Zot or Quay, that also have way more features than I actually need in this specific use case. If all you need is a mirror however, it is actually really simple to set up a bare minimum low-maintenance registry for this purpose in Kubernetes.
Hello World
Welcome to my blog! I will primarily be writing guides related to Kubernetes, OpenShift and cloud native technology with the main theme being guides and documentation I wish I had during my work.