Since pods created in k8s are ephemeral, we are able to get the data as long as pods are alive, but if pods are terminated data stored in it completely lost and it cannot get back, for that we need to mount a volume to write the data into that of a pod. To do that we have different ways. Let’s look at those things. Host path: with this type, we can configure a directory on the host itself (node) and specify a path /data. Once the volume is created, we mount the volume to a directory inside t...

Stateful sets are similar to deployments, they can scale up and scale down, they can perform rolling updates etc. All most it performs similar functions like replica sets and deployment sets. but there some difference as well, in stateful sets pods are created in a sequential order, that means when the pods are deployed, 1st pod should be in running and ready state after that new pod will be created to match the desired replicas. So that makes our life easy to understand which pod is created 1st...

Till now I have given blogs on k8s objects, services, namespaces, ingress etc. but where to execute and implement all those, yes, we need a k8s cluster for that, if you have it already go n execute, if not, here is the solution for you.

If you have deployed different applications on k8s cluster using various objects like deployments, pods, services etc. all the info about cluster is stored into ETCD cluster. If your application is using persistent storage that will be considered as another backup scenario.

Taints and tolerations are used to restrict the pods to schedule them onto respective nodes. There is nothing to do with security.

Assume you have 3 nodes cluster of which two of them are having lower hardware resources and one of them is larger node configured with higher resources, and there are different kinds of workloads running in our cluster, and you would like to dedicate data-processing workloads that require higher horse power to the larger nodes , as that is the only node that will not run out of resources in case job demands extra resources.

The k8s node affinity feature is to ensure pods are hosted on a particular node. As mentioned in previous blog large data processing nodes are into node-1. we achieved that using node selectors. As I mentioned that we cannot provide advance expressions like large or medium / not in small nodes.

Ingress is a resource, which exposes the http and https from external sources to the services within the cluster, by adding the rules in the ingress resource for routing the traffic, where traffic is controlled by ingress controller.

The Kubernetes RBAC (role bases access control) system helps us in defining set of rules in controlling the access among users across resources. Kubernetes cluster by default has two name spaces, “default” and “kube-system”. Creation of additional namespaces is also possible for organizing and separation of work based on our purpose which I have already explained in previous blog on namespaces (“refer that for more details”).

A default namespace is created automatically when the cluster is being setup. To isolate or prevent a user from accidentally deleting the services, Kubernetes creates certain pods for its internal purpose like networking solution, DNS service etc.