It was indeed a great session by the industry experts and got to learn lot about how Kubernetes and OpenShift is used inn industry to solve the real world use case.

I would like to mention some key takeaways from the yesterdays session:-

1. CVS stands for (Centralized Version System) is mainly used for version control system(vcs) where in the multiple version of the source code is rolled out. It keep the record of all the changes that is done to the code or set of files. It is also referred as Concurrent Versioning System.
2. CVS system works on file system and git is working in DVS (distributed version system)In CVS if one can only change/commit centrally i.e. if they cannot clone the repo and commit locally. This is a huge disadvantage for the developers working in teams. also working in git more easy.
3. There are different environments for an application:

Engineering cluster — Serves as a playground SIT (System Integration Testing) — where one tests the application when it is almost ready to be deployed

UAT (User Acceptance Test) :- The closest environment to production where there are real workload tests.

Production server :- where the actual app is running and accessible for public use.

4. Requests and limits are used to control the hardware resources(CPU and memory). Requests are what the container is guaranteed to get. Limits, on the other hand, make sure a pod never goes above a certain value. If there are no limits set then there are chances of leaks happening, so one must always set limits.

5. I got to know lot of things about SCC. Security context constraints(SCC) allow administrators to control permissions for pods.