Articles
kubectl basics
Here are some of the basic kubectl commands.
Generic Kubernetes manifest for web application deployment
Deployment name, container registry and service port are externalized, making this manifest general-purpose
Creating a private docker registry for Kubernetes
A docker registry can be run easily using as a docker container using docker itself.
Kubernetes persistent volumes
Applications deployed on a Kubernetes cluster run inside containers. As a consequence, their file system is that of the container, which means that if the container is removed, the data it contained is lost.
Deploy a Neo4J instance in Kubernetes
Using this manifest, a Neo4J instance can be deployed in a Kubernetes cluster
Passing variables to Kubernetes manifest
When using kubectl apply, environment variables in Kubernetes manifests are not parsed. For this to happen, the envsubst command can be used.
Kubectl pull new version of image without changes to manifest
When using kubectl apply using an already applied and unchanged manifest file, nothing happens on the Kubernetes cluster. However, deployments can be configured so as to always pull a new version image upon restart. This is achieved using the, <code>imagePullPolicy: Always</code> parameter:
Kubectl create deplpoyment and service at same time
Simply add entries for both the deployment and the service in the same manifest, separeted by ---
Updating Ingresses to networking.k8s.io/v1

Using Ingress with the extensions/v1beta1 API has been deprecated in Kubernetes 1.14 and will be removed in 1.22. This article presents how to update an existing manifest to the new API, networking.k8s.io/v1.
Microk8s manage SSL certificates DNS entries
Microk8s provides settings to add a custom domain to its DNS settings. This article presents how to do so.