What is OpenShift?
OpenShift is an Open-source container application that is based on Kubernetes, It holds full-stack automated operations to manage hybrid cloud, multi-cloud, and edge deployments.
It lets us monitor container resources and container health, manage users, work with operators, and so on~
OpenShift provides a CLI that supports a superset of the actions that the Kubernetes CLI provides.
Containers Vs Virtual Machines:
What is a virtual machine?
Virtual machines (VMs) are a technology for building virtualized computing environments. They have been around for quite a while and are considered the foundation of the first generation of cloud computing.
What are containers?
Containers are a lighter-weight, more agile way of handling virtualization. Rather than spinning up an entire virtual machine, a container packages together everything needed to run a small piece of software.
Why choose containers?
In traditional virtualization, a hypervisor virtualizes physical hardware. The result is that each virtual machine contains a guest OS, a virtual copy of the hardware that the OS requires to run, and an application and its associated libraries and dependencies.
Instead of virtualizing the underlying hardware, containers virtualize the operating system (typically Linux) so each individual container contains only the application and its libraries and dependencies.
Containers are small, fast, and portable because unlike a virtual machine, containers do not need to include a guest OS in every instance and can, instead, simply leverage the features and resources of the host OS.
Just like virtual machines, containers allow developers to improve CPU and memory utilization of physical machines.
Containers go even further, however, because they also enable microservice architectures, where application components can be deployed and scaled more granularly.
This is an attractive alternative to having to scale up an entire monolithic application because a single component is struggling with load.
Containers provide a level of flexibility that is perfect for the multi-cloud world. When developers create new applications, they might not know all of the places they’ll need to be deployed. Today, an organization might run the application on its private cloud, but tomorrow it might need to deploy it on a public cloud from a different provider.
-Container technology is used to isolate applications in order to perform various tasks
-Containers consume very less amount of compute resources so they are efficient in terms of deploying individual applications and can be provisioned within no time
-Kubernetes (or K8s for short) is an open-source container orchestrating tool which can also perform tasks such as monitoring, managing, scaling the containerized application.
- PODs are the smallest units within the Kubernetes cluster, these consist of one or more containers, in short.. its a deployable object
-Once deployed, k8s will monitor the pods
-VMs are designed in a manner that these are software that runs on physical servers for emulating a particular type of hardware system
-These VMs run as a unique guest operating system
-In comparison to VMs, Containers are exceptionally light and can be generated within moments of notice
-OpenShift is an Open-source container application that is based on K8s
-Some of its most used features are:
Autoscaling pods, high availability, operation hub, IDE integration, easy-to-use command-line tool and web UI, compatibility with kubectl commands, etc.
-Application platform is a framework of services in which the app’s program depends on it from the standard operations
-PaaS lets us focus more on application and data rather than wasting our time on provisioning our envi
-S2I or Source-to-image is a toolkit that consists of a workflow to build reproducible container images from a SC
-it can produce ready-to-run images
-Service mesh is a configurable low latency infrastructure layer designed with the high vol of network-based in-process communication in mind
-PodMan is a container engine similar to docker but more secure, The commands in Podman is mostly similar to docker
-But unlike docker, podman runs on a daemon-less architecture
-So each user running Podman can only see/modify their own containers
I’d like to thank Mr. Amel Mathai, Mr. Daleep Singh Bais, and Mr.Abid Mattoo for sharing their vast knowledge and experience with us.
And most of all, I’d like to thank Mr.Vimal Daga Sir, Preeti Mam, and the rest LinuxWorld Informatics Pvt Ltd. team for organizing such a great session.
Thank you for the time~!