Let us check what is Git and GitHub and how they work. To understand this, let us imagine a scenario where we are writing a document or a piece of software or app or just an essay or poem.

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.

Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is commonly used for open source and commercial software development.

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”).

Subversion (SVN) is a central version control system (VCS) while Git is a distributed version control system. SVN does some things very well and has been a great source control system. But the features that Git brings – distribution, performance, easy branches, easy merges, stash – are hard to pass up. These two tools have some big differences, but git has more advantage than svn, which is why a lot of companies are now migrating from svn to git. There are several ways to do migration process ...