Tagged: kubernetes

Having event deduplication is a game-changer for several reasons, that finally made the operator writing possible. Let's have a look.

As I already mentioned, I wasn't too happy about the currently available DNS operators out there that integrate with let's encrypt. What I wanted was one that works right of the box, and allows me to add new Ingress objects, and magically generate their TLS certificates. I'm going to break down in a small mini-series of articles on how I ended up implementing it.

As I already mentioned, I wasn't too happy about the currently available DNS operators out there that integrate with let's encrypt. What I wanted was one that works right of the box, and allows me to add new Ingress objects, and magically generate their TLS certificates. I'm going to break down in a small mini-series of articles on how I ended up implementing it.

If you already have some containerized infrastructure running with docker-compose, or just plain docker containers that are provisioned by a config management tool, you definitely want to switch to Kubernetes. Here's how I did it.

After we install the snap of microk8s, we notice that the default .kube/config is not there, furthermore we need to use the microk8s.kubectl binary to access it. One option is aliasing the kubectl to microk8s.kubectl, but that has its own drawbacks, such as not being able to use it in scripts. Furthermore if we already have a .kube/config we'd want the configs to be merged. So how do we achieve that?

If you execute the default bare metal installation of an Nginx Ingress server you'll find out that it's actually not listening on the "normal" 80/443 ports, but rather on some client ports. What's worse is that there's a rather small limit for the proxying, so if you're exporting a binary registry, and you want to publish binaries from outside the cluster, you're in trouble. Here's how to fix this.

Let's assume you're spinning up pure docker containers in your Kubernetes cluster. Not pods, but docker containers. For example you're using docker.inside in your Jenkins builds, and your Kubernetes is hosting the Jenkins instance. You'll notice that your docker container can't access services in your cluster.

If you want to try Kubernetes locally you're in for a lot of trouble. Installing it requires you to deal with changing apt repos, installing docker, installing kubectl and kubeadm, provisioning, installing networking, configuring the keys for cluster access, etc. Fortunately Ubuntu offers an easier way, via snaps.

As we enter 2019, I am using clouds a lot - the Germanium infrastructure is on Kubernetes, my last project was on AWS, I stopped using Java in my personal projects, and started learning Cobol for work. Here's why.

Kubernetes provides ConfigMap objects that allow storing key value pairs into its own etcd storage. The backup of Kubernetes also includes then those objects. Mounting a single key from the config as a file in a container is also straightforward. We'll see in this article exactly how.