Share and manage Kubernetes resources between namespaces Sometimes that’s hard to manage Kubernetes resources that you need to have them in multiple namespaces (e.g. pullSecrets, TLSCerts or some shared web server plugins) to handle that we have to use a Reflector in our cluster, I found one on GitHub, but I had two problems with that, first you need a source resource to annotate or label but sometimes you are creating resources yourself and there is no need to have an extra namespace for starting point, So I made a K8s Operator that is able to handle both ;)

Today I will show you the power of minimalism at first we will talk about Kubernetes a bit then we will talk about what is k0s and comparing it to it’s alternatives next I will show you two simple example of making a cluster on a single node or using k0sctl Before reading this section you should have a bit knowledge about docker Let’s talk about Kubernetes a bit K8s is a container orchestrator it’s like a conductor for containers to manage your cluster and for example decide witch container should go where.

This Post will give you an introduction to Docker BuildKit & Buildx What is buildkit? Buildkit is a project made by moby it’s working on top of docker to give you ability to have custom volumes while building images (caching, secret, etc.) Using buildkit you cat easily cache package managers (even if you change packages), change network mode per-layer, secret files only for one layer, ssh keys (cloning a repo), or running one layer as privileged, and also faster than normal docker :)