Hi, everyone. This is Aisha Kim and I am starting my session um on OD uh just start starting now and I'm sharing my presentation on the screen.Um I'm a software engineer at Redhead and uh please let me know if you face any problem related to microphone or screen sharing and everything. Uh So let me begin with the OD. Um I'm gonna give uh the basic overview in this presentation of OKD and try to also let you know about how we can install the OKD in our um in any cloud. Um I I will be using the vmware vsphere and try to install the OKD on that. So in this uh slide, I'm gonna give you the uh your overview for OKD demo installation and we're gonna discuss about the operators and operator hub uh which is uh uh including the latest features in OKD four and instead of OD four and also OKD and Fedora Kos Collaboration. Um So first of all, OKD, openshift Cuban is distribution is a cloud based Cuban is container platform. Um The foundation of OKD is based on Cubans and therefore shares the same technology as a cluster administrator you can use the OKD installation program to install and deploy a cluster by two methods, installer provision method which is a installer based installation configuration and user provision infrastructure which is manual configuration.

Uh Installer provision infrastructure is a largely automated install processes uh where the installer is responsible for setting up the infrastructure where the user provision infrastructure requires you to set up the base infrastructure. Um OD supports installation on bare metal hardware, a number of virtualization platforms and a number of cloud uh platforms. So you need to decide where you want to install OKD and that your environment has sufficient resources for the cluster to operate. If you want to install on a typical developer workstation, then codere containers uh maybe a better options. Uh as that is a cut down installation designed to run on limited compute and memory resources. Um So um OD is a platform for developing and running containerized applications.

Uh It's a design to allow applications and the data centers that supports them to expand from just a few machines and applications to thousands of machines that serves millions um of clients with its foundation in Cuban is OK. D uh incorporates the same technology that serves as the engine um for massive telecommunications, streaming videos, gaming, banking and other applications. Um Its implementation in open open redhead technologies, lets you extend your containerized applications beyond a single cloud to on premise and multi cloud environment.

So in this slide I'm gonna give mo uh little bit dig deeper into the architecture of OKD and how uh it's built and what um the opera operating system we are using for openshift or for OK. Dod provides enterprise ready enhancement to Cuban and I'm gonna talk about the enhancement in OPD four, you can deploy OKD clusters to a variety of public cloud platforms or in your data center. As I already told you, uh major components in O CD come from Fedora and related redhead technologies. OK. D benefits from the intense testing and certification initiatives for redhead enterprise quality software development is open source and the source code is available from public uh software repository.

For example, github. Uh This open collaboration helps rapid innovation and development. Although uh CBA is excels at managing your applications but it doesn't specify or manage platform level requirements or deployment process. Um powerful and flexible platform management tools and processes are important benefits that OD four offers.

Now, I'm gonna talk about some unique features and benefits of OKD four. For example, custom operating system. OK. D uses uh Fedora Co where we call FO as well. Uh a container oriented operating system that is specifically designed for running containerized application from OK D and works with new tools to provide fast installation operator based management and simplified upgrades. Um Federal includes ignition which OK. D use as a first boot system configuration for initially bringing up and configuring machines. Um Cryo Cerne is native container runtime implementation that integrates closely with the operating system to deliver an efficient and optimized. Cerne is experience. Uh Cryo provides facilities for burning stopping and restarting containers.

It fully replaces that Docker container engine which was used in OKD three CL, the primary co node agent for certis that is responsible for launching and monitoring containers. In OPD four, you must use FUS for all con control planes machines. Um But you can use redhead enterprise Linux as the operating system uh for compute machines which are also known as worker machines. Um If you choose to use real workers, you must perform more system maintenance than if you use Fedora Cor for all of the cluster machines. And then I'm gonna try with the OK demo installation on beam where we swear um the installation uh I can start the process, how we can uh create our configuration file. Um But the installation process takes time and most probably we will be end this uh this presentation and installation will still be running, but I would still uh be still like to um start the cluster uh start the uh installation process. Um I'm already in my virtual machine.

Let's see. The surgeon. You stop. Mhm Sticking just a little time to access my virtual machine where I'm gonna install um my OKD cluster. Um Yeah. So OK. So here we go. Um Well, I have uh already um set up uh uh OK. So I, I want to begin the process from the start so that it will be uh more easier for understanding. For uh first of all, we have to download um the openshift uh install and Openshift client and QC TL for the OKD. So for this, we can use this command OC ad M release extract and using the latest release for OKD, which is uh currently 4.10. It will take some little bit of time and our files are will be downloaded. Yes. So they are downloaded and I want to extract them. So now we have downloaded the binderies of openshift install openshift client and cube CTL. And for that, we need to move them to our user local bin. So now we have openshift client version 4.10 0.0 is downloaded. Um So first of all, we need to create the directory for our cluster, which is uh uh it can be anything, your user name or anything. And then I will be creating my install for config file for that directory. So first of all, like I am, I'm, I'm installing the uh my um I'm installing my cluster on the vmware vsphere. And of course, that's uh that should be connected with your virtual machine. So I'm using my public ID, using the VSPHERE.

And then we need, I need to add some information about the V center. I mean the details for my that where the cluster should be installed, my user name and password details as well for that particular installation in my V center. So now select the data store and now select the de se um the network for your cluster. And according to the settings and configuration for my uh V center, I'm gonna be using the deaf segment and then virtual IP address for then API it also depends on the settings of your Sare Center and for English, so the base do remain will be the Choler name. OK. So for the openshift OKD installation because it's a community version. So you don't need a pull secret. Um You can use some random pull secret for that. For example, I can share here in the, in the chat. You know how, how I can share the chat. Yeah. So that was the secret that I have pasted here, which is fake. Cool secret, but it it's a valid DML. So now my install config file is created for my installation which is like that. And um and then I'm gonna be uh so that my uh uh installation configuration file is created. So I'm gonna be starting my uh openshift install, create cluster and uh dietary Eline. So the installation will be begin to start.

And II I, I'm not sure, I don't think so that I would be if because it takes time, it takes approximately uh 20 to 30 minutes to installation to complete. So meanwhile, so the installation is started. If you face some errors or something like that, then you can search them those errors or those issues to fix those. Meanwhile, we can go back to our presentation and I'm gonna be discussing about uh operators and operators hub for OKD four. So that's a really interesting topic.

OK. D four edits some amazing operators to automate the infrastructure operator, automates what Qbert is uh operate, what are operators, first of all, so operator automates what Qbert is does on behalf of a user. And operator extends the Qbert functionality um to automate the management of the entire life cycle of a particular application. Um It's a custom C is controller that uses custom resources to manage applications and its components. Um Operator SDK is basically a framework to build an operator using Golan and, and helm um our NCB. Uh And we're gonna talk about uh So that's the basic operator SDK. We I'm gonna be talking about how operator operators are leverage, leveraging openshift and which manages the application.

But the cluster itself, for example, establishing a cluster on autopilot where cluster is managing itself by using the um core main core operators of Openshift. So first of all, I'm gonna discuss about cluster version operator. The main operators, cluster version operator basically make sure that all essential core operators are presented which I'm uh all uh essential core operators are present which I'm gonna discuss in this slide cluster version. Operator also maintains and updates the version of the core operators uh QBPF server, Qbe controller manager cube scheduler et these operators ensures the core components of Qbert is configured for a cluster cluster network operator installs and upgrade upgrades, network components on Openshift its cluster, it follows the controller pat pattern.

It reconciles the state of the cluster against a desired configuration which includes ensuring if the CNF plugins are installed or Sdn is configured in openshift. The cluster network operator runs very early in the install process. Uh while the bootstrap A PS server is still running.

Uh openshift operator uh is an openshift component which enables extent access to cluster service by configuring increased controllers and ensure the routs are set up. English operator implements the openshift Ance controller API and image registry operator. It manages all the configuration of openshift registry including creating storage uh on on an initial start up. The operator will create a default image registry resource instance based on configuration detected in detected in the cluster. For example, what cloud storage type uh to use based on which cloud provider and the monitoring operator manages and updates. The Promes based cluster monitoring is and stack deployed on the top of Openshift. And I'm gonna be talking about the operator hub is a, it's a, it's a new home for the Cuban community to share operators. They are all the operational operators and operator lifecycle manager is like a cluster version operator for all the optional operators of operator hub operator, lifecycle manager uh helps user to install update and manage the life cycle of certs operators. And it takes care of operating scope uh cluster wide or names space only ensures it can be updated um manually and manages permissions to use the install operators for the openshift cluster.

Um For example, storage operators based on root dot IO pipeline operators based on TECT to ARGO CD Q word Grafana. And they are all the uh uh optional operators. So these all are operators where uh we, you can use with the O with the OKD, which is a community version uh not uh of openshift. So you, but still, you can, we already have already a lot of integrated main operators and also uh other opt uh optional operators that you can use from operator hub. So I will be, I think I we are already out of time um But still I will be try to finish this presentation as quickly as possible instead of OKD four. We have current stable releases, 4.4 0.10 and we have document for sub working groups and we have multiple uh groups for OKD uh codere containers uh uh on OKD working group virtualization. So, working group. So we all have uh working groups uh for the OKD and join us for our working groups. You are, you all are welcome to join and you are all are welcome to collaborate. If you want for in OKD and for, for um Fedora Curves.

And I'm gonna be sure about the slack links for OKD working groups. We have openshift, these are the Slack links, Openshift users cle dot dot com. And you can also issue track issues on github and we have biweekly video conference meetings. Uh and you can also subscribe the calendar to get the invites for the meetings if you are interested. Um We have also have Fedora Co working Group where you can also uh use the same information and join the meetings for Fedora Co collaborations. And um I think we are almost out of time. But if still you have any questions, please let me know and I would be really happy to answer you. So, uh thank you so much for joining the meeting and bear with me. Um And I hope you all gonna enjoy. You have already enjoyed this presentation. Thank you. Bye.