Adventures in a Cloud Native Landscape

Whenever I hear a debate about the pros and cons of Argo CD and Flux as preferred GitOps solutions, invariably it’s Argo CD that wins out.

I recently had cause to test out cert-manager using the Kubernetes Gateway API, but wanted to do this using a local cluster on my laptop, based on kind.

I was recently struggling to add a single annotation to a Kubernetes object definition, using a JSON Patch with Kustomize, when I stumbled on the JSON Pointer syntax.

I’m putting this here in case anyone runs into the same problem as I did (and, seemingly, others).

This article follows on from an introductory article that discussed the chicken or the egg paradox when it comes to bootstrapping GitOps agents into Kubernetes clusters.

Following on from an introductory article on the merits of bootstrapping GitOps agents into Kubernetes clusters, this article looks into how this can be achieved with Flux.

Since the term was originally coined back in 2017 by Alexis Richardson (CEO of Weaveworks), the GitOps philosophy has struggled to find a coherent, consensual definition.

Docker provides a comprehensive API and CLI to its platform.

When Docker v1.10 came along, there was a fairly seismic change with the way the Docker Engine handles images.

Docker images are the templates that derive the nature and behaviour of a container, and Docker stores these images in repositories on hosted registries.

Containers created and managed by the Docker engine are able to provide the service that is running inside the container, not only to other co-located containers, but also to remote hosts.

We’ve looked at five of the six available namespaces provided by the Linux kernel in a series of previous articles, and we’ll take a look at the final namespace, the USER namespace, in a future article.

The IPC namespace is used for isolating System V IPC objects, and POSIX message queues.

So far in this series, we’ve looked at isolating processes in PID, mount and UTS namespaces.

The UTS namespace is used to isolate two specific elements of the system that relate to the uname system call.

In the last article about namespaces, we looked at the PID namespace.

A PID namespace isolates process ID (PID) numbers, thereby allowing different processes running on the same Linux system to have the same PID.

The container abstraction has made a big entry into the world of software development, offering a method for streamlined feature delivery.