The most obvious reason for a Kubernetes cluster upgrade is the software aging. We must upgrade the cluster on a regular basis to stay up with the newest security features and bug patches, as well as to take advantage of new features that are published on a regular basis. This is particularly crucial if we have installed a very old version or if we want to automate the procedure so that we are constantly up to date with the newest supported version. In this blog, we will cover How to Upgrade the Kubernetes Cluster.
The etcd server is the only stateful component of the Kubernetes cluster. Kubernetes stores all API objects and settings on the etcd server. etcd backup is enough to restore the Kubernetes cluster’s state completely. Kubernetes disaster recovery plans often include backing up the etcd cluster and using infrastructure as code to create new cloud servers. In this blog, we will cover How to Backup & Restore the Etcd in Kubernetes.
Configuration files are meant to be separated from the application even though it is not mandatory. All the sensitive information regarding your application must be stored and kept safe. The configurations are the particular bits of data like API keys, tokens, and other secrets. You may be tempted to hard code these data into your application logic. This might be acceptable in a small, standalone application, but it quickly becomes unmanageable in any reasonably sized app. K8s also provides a more conventional approach to configuring your applications in the form of environment variables. In this blog, we will be covering how to configure applications using Configmap and Secrets in Kubernetes
Do you know why is Kubernetes is the talk of the hour? We need to look at the advent of containers and microservices, which brought us excellent software development and infrastructure capabilities. K8s performs automation with ease, and the Kubernetes Operator aids them a lot.Kubernetes’s idea was to automate stuff, but then if we need Operators, what’s the whole point of K8s? This blog helps you decode the need and importance of Operators.
Kubernetes monitoring is a method of examining and reporting the health status of cluster components. So, the process helps track the utilisation of cluster resources, including memory, CPU, and storage. And, talking of open-source tools like Prometheus for Kubernetes monitoring and Grafana for visualising have become the numero uno go-to tools!
Dashboard was developed which definitely has gained more attention of people who were looking at Kubernetes in dilemma. The Kubernetes Dashboard comes under the Cluster Setup of the CKS exam topics. If you are looking for a resource to learn what exactly is a Kubernetes Dashboard, what does it do, and how to install it then, you have arrived at the right place where you find a thorough guide to all of it.
In a recent study, scientists have concluded that the Coronavirus also infects the Kubernetes pods 🤯 That is why we need to do Health Check for Kubernetes! Of course, I was kidding; but a health check or probe is indeed a method of checking the health of a Kubernetes pod. However, Kubernetes Readiness Probe and Kubernetes LivenessProbe help us with the health status of our applications. So, before I get on to show a step-by-step hands-on, I will also cover what Kubernetes Readiness and Liveness probes.
Kubernetes has 3 types of services viz. ClusterIP, NodePort, and LoadBalancer. The Ingress exposes HTTP/S routes from outside the cluster to services inside the cluster. So, one thing must be clear to you now that the ingress isn’t a type of service that Kubernetes offers. Whereas the Kubernetes Ingress Controller is pledged to manage the traffic and the ingress mostly with a LoadBalancer.
Kubernetes is the mood of the developers right now! It is trending like never before. Kubernetes a.k.a K8s is an open-source system for managing containerized applications across multiple hosts. It provides basic mechanisms for deployment, maintenance, and scaling of applications. Everything in Kubernetes is all about Deployment.
Pods are the smallest deployable unit of Kubernetes where we can run our applications. Scheduling in Kubernetes is a core component as it aims to schedule the pod to a correct and available node. If you want to understand why Pods are placed onto a particular Node, or if you’re planning to know types of scheduling then this blog is for you!