When come to operating Kubernetes, we need to ensure the cluster backup is one of the key operation as part of our backup strategy. We need to properly backup and secure the application data which is typically stored in persistent volumes. On the other hand, we need to backup the etcd data because it is the operational data store that is used by Kubernetes in order to operate accordingly. In this post we are looking at how to schedule the etcd data backup using out of the box Kubernetes features.
There are a few approaches to expose your applications to the world outside of Kubernetes cluster. One of them is using Ingress Controller. We are going to learn how can we use Nginx Ingress Controller to expose container applications running on top of Raspberry Pi Kubernetes cluster.
In a perfect world, we would prefer to implement microservices to be stateless. This stateless approach eliminates a lot of problems towards maintaining the storage for the applications data. However, we are not in a perfect world. At most time, applications need to deal with data and keep them on storage for long term references. We need persistent storage solution so that the applications data can survive containers (or systems) restart or crash. Kubernetes provides this type of storage support in the concept of volumes. We are going to look at how can we configured storage for Kubernetes on Raspberry Pi 4.
In my previous post, I briefly talked about event-based architecture for payment platform modernization and why the modernization is important to the industry. In this post, we will dive into details of the key capabilities to consider for the payment platform modernization. The capabilities covered in this post may not be the complete list but it definitely serves as a good start.
Creating your own version of container image for Kafka Connect for OpenShift is pretty straightforward with simple few steps as outlined in this article.