Industrial Use Cases for Kubernetes from Experts : An Insightful Session

Hello Guys, I recently attended a session based on Industrial Use Cases for Kubernetes by Experts conducted by Mr. Rushil Sharma, Mr. Vijit Kuntal & Mr. Neeraj Bhatt.

Session Learnings

CVS

  • Centralized Version Control System
  • Works on File System

Git

  • Distributed Version Control System
  • Works on Repo/Module level

Why is Git preferred over CVS ?

  • Provides functionality of branches and thereby it provides parallelism i.e., working on multiple features at a same time
  • Provides Rest API implementation
  • Easy to reconcile

SCC(Security Context Constraints )

What does SCC controls?

  • Whether a pod can run privileged containers
  • Sharing host directory as volume
  • Set SELinux Context
  • UserID the container could run
  • Host Namespace and networking
  • Allocation of FSGroup that owns the pod’s volume
  • Configuration of allowable supplemental group
  • Does container requires the use of read only root file system
  • Usage of volume types
  • Configuration of allowable seccompt profiles

Fields configured in SCC

  • runAsUser
  • Volumes
  • allowPrivilegeEscalation
  • defaultAddCapabilities
  • Priority
  • User

Other Important Concepts

Global Traffic Manager : It is designed so that Internet users can more reliably get to your websites or any other IP application.

Chaos Testing : It is the process used by companies by tools like ChaosMonkey in which certain situations like network driver going down, volumes becomes inaccessible and many more and other these situations, the behaviour of cluster is checked.

Engineering Cluster : It is the playground in which cluster which is not deployed could be deployed for testing.

CPU Request : It is defined as the number of resource that would be guaranteed to the pods for lifetime.

CPU Limits : It is defined as the maximum resource that could be allocated to a pod by hardware.

CPU Leaks : It occurs when the pod doesn’t release the resource and gives it back to the hardware due to a bug in process after the execution of process takes place. Also if the CPU limit is not set, pod would keep on requesting the resource till it reaches the full capacity of the nodes.

Namespaces : It is defined as the environment created for a user for managing their applications and programs.

At the end , I would conclude that it was blessing to be part of this wonderful session by experts that gave an insight to the industrial use case regarding Kubernetes.

Thank You !!!