Kubernetes `CronJob` define periodic scheduled tasks in your cluster. In my new article, I explain how to use a CronJob for persisting pod log data in simple text files.
Kubernetes service account define fine grained access to any Kubernetes resource, including namespaces, pods and log data. In this article I explain how service accounts work by using curl statements against the API. It was a great educational experience! Read what I learned.
In Kubernetes, Pods are dynamic and ephemeral. And so is their log data: When a pod terminates, its gone. Retaining log files can be complex - do you really need the ELK or EFK stack? If all you need are plain text files, then my KubeLogExporter can be your solution.
Your Kubernetes cluster provides a finite amount of resources such as CPU, memory and storage. Carefully crafting resource limitations and health checks keeps your apps running.
A private Docker registry simplifies managing your application deployments in Kubernetes. Read my tutorial to setup you own private Docker registry in a few minutes!
Creating a Kubernetes Cluster from scratch seemed like a daunting task to me. With the lightweight Kubernetes distribution [K3S](https://k3s.io/) it becomes a one line bash script per Node!
#Serverless functions are resource effective: Deploy and pay for consumed resources only. With #openfaas, write functions in #NodeJS, #Python, #Go and many more. Read how to redesign a microservice as a #serverless function
The #openfaas framework allows you to write serverless functions #nodejs, #python, #go, #java and other languages. It provides you with templates that are effectively Docker containers. I wanted to understand what those Docker container do and how the execution environment for functions in any of those languages is provided for you. Read more about this in my new blog post.
