OpenShift MultiNode Cluster Deployment Step By Step Part-1

hello friends my name is Suresh I'm a senior DevOps engineer today I'm going to demonstrate how to deploy the open shipped origin cluster by using 3.9 buzzer in this video I will demonstrate how to deploy open shaped origin 3.9 cluster step by step this is the agenda which I'm going to follow in this video I will set up the four VMs from this scratch then download the open shift in Siebel a git repo from the github because I'm not going to do the manual installation I'm going to use the in cebu then I will create my own inventory file for the deployment then I will run the prerequisite playbook to validate the environment the four node cluster then I will use the playbook to deploy the open shaped cluster once the deployment has been completed I will create a admin user so that I can log in using the web console or from the different machine by using the OC client command then I will create a one our project may be by using the web console or you can use the OCC alaikkum on to create it then we'll deploy an application in that project and we'll try to access that application by using the URL which will be provided by the open shipped environment so keep watching so let's do the fastest tab so what for V MSP have so I have set up my for PM's in our virtual environment by using the VM be a walker station so you can see here this is my master node this is my infra node this is my node one and this is mine order to let me give you the overview of these two these four machines this is the master so you can see I have 2gb of RAM so it depends on your resource capacity I have given to processor and 100 GB of hard drive and this is my network which is running on the brains mode so that I can access the dashboard from my laptop directly the same configuration I have for the infra note as well so here 2 GB of RAM 2 processor same configuration note 1 I have same and for note 2 as well so I'm thinking you must wondering like why I have master and infra so what my diagram is I'm going to use 4 nor to deploy the open shaped cluster my API will be run on the master node where my web console and API controller scheduler will be running here I have dedicated my infra node especially for the registry which is the integrated registry container for the openshift and the routers which is going to forward the traffic into the node 1 and node 2 for example you are deploying the application so those applications will be deployed on node 1 and node 2 so how the external customer or clients can access the application so that traffic will come from the infra because I'm going to host my route on the in front load so yeah this is the dedicated node or in my case I'm not using any high availability for these nodes because I don't have much resources available on this laptop so if you want you can have the 2 in front roll with the replica of 2 routers so yeah you can decide that one later on like which network traffic you want to filter for the node 1 and node 2 accordingly this is the node 1 where we will run our pods or containers you can say and note 2 as well so these are the 2 node node 1 and node 2 dedicated for the applications or containers infra note will be dedicated for the registry and routers and master node will be for API n tub consults so let's access this one so I have here my shell so you can see I'm going to access my master first this is the master as a search infra this is my intra node 1 yeah and note 2 yeah so right now I'm using the send to s you can see release so it's sent to a 7.5 so you can choose that one what you have to do first I have created a one file here as well so this is the environment IP address and all those things could be different so what IP address I'm using here it's a 3 this one this is 1 3 2 here 1 3 3 and 1 3 4 so let me put that one in a sequence so here this right so this is the IP address this is the host name CPU and all those configurations so you can check it here this is the IP address and you can see I have not configured the DNS to resolve a host name so I have used DTC a hosts file to preserve all these names they are communicating to each other so you can check by using like master yes infra yes node 1 and node 2 so this is the configuration I have done on my all four nodes to resolve each other by using the names yeah so if you want you can perform like these stab which I mentioned here you can set the hostname this is the command for the master for other nodes you can use the same command and configure the hostname then you can configure the IP address so in my case master IP address is this so accordingly you can configure the IP addresses for rest of the nodes DNS I think in my case I have this one so yeah you can confirm that 1/80 see result dot can't so you can see yeah this one is my name server which is running in my router yeah and this is the global DNS server from the Google so this is the confirmed configuration I have done on all the nodes rest if you are doing some changes here you can put down your connection then we load these settings and up your connection and then configure your UTC host file so let me put here as well so here oops this is 1 3 2 and this is 1 3 3 and this is 1 3 4 so this is my current environment so what you have to do fast you have to update your all the nodes so I am just starting from the master so they say cm update master configuration is already demonstrated to you few packages I think I will have here because recently I have updated my D servers so you can see here this is the infra this is the node one and this is the node two right so these servers will be updated here second you can see here this is the command like maybe in my case I have just a few packages and there is no Cardinal so maybe when you are going to update your system you will get the new kernel so you can use this command to check if both of the kernel this is your installed kernel this is the current kernel which you are using in my case both are the same so I don't need to be reboot the system in your case if these two values are different then you have to reboot the server remember that because as I mentioned I have just rebooted my all these servers oops yeah you can see here value our value is same so I don't need to reboot here also yes and here also yes no need to reboot okay then you can see here I mentioned ok now once the system come back online you need to install these packages so these are the dependencies so you need to install this one on your master node as well as infra and node one or two so I have installed all these packages previously so nothing to do here much right then this you need to install the EPL repository you need to enable this one and then you can also configure the openshift so in my case I have all these repositories pre-configured so you can check it here yum wrapper list so this is the center's this is the base update and all so what you can do you can download this package on masternode yeah installed here this one here and here as well so it says is already installed so nothing to do if you have done this one so what you can do you can disable this repo because we don't need this one anymore we require just a specific packages to be installed from this EPL not all because sometime it will conflict other packages then you can also create the OpenShift wrap oh I don't think so you require this one because it will be configured by using the ansible so you can configure this one from here or you can use the in Siebel to configure this repo on all the hosts so I am using here done here so what I'm doing here I'm just sending this one from this location to my root add infra node : same location yes and node 1 and node 2 okay so we have copied our open shipped dot rapper file on master on infra a node 1 and node 2 so let's confirm this one so we can check Katz let's see t see m dot R opposed dot D open shipped or trap oh yeah so let me copy this one put here yes put here yes and put here yes ok now [Music] what we have to do we have to make sure that the network manager service should be started because open shipped using the network manager not the legacy network service so in my case the network manager is already started so I'm just checking the status here yes it's running here it's running and end enabled as well on all the nodes so I'm just verifying this service on all the nodes yes in your case you can start or enable accordingly let me check here the darker so we also need the docker service on all the nodes so what we can do we need to check it here on master so you can see docker is not started it just installed the package but not started so we need to start the docker so let me start the docker on master on infra yes and on node 1 and on note 2 yes now you need to enable so let me put that on enable so if you are free booting this system it will be enabled by default and let's check the status one more time here yes running here running here running here running ok we can confirm that by using docker - version oops yeah so openshift using 1.13 person of the talker this is the client and this is the server ok now our node has been prepared so what we can do we can install the in Siebel package on the master so remember you just need to install the in Siebel package on the master from EPL wrapper so a PE l repo by default is disabled so we have to put that one enable rapid this one just to install in Siebel and dis package so remember that you have to just install this one on master node not on infra node 1 not 2 yes it's installing and you can confirm that which version of in Siebel you are using here so it's a 2.7 so this is the version of the NC Bell I believe this is the latest version of in Siebel previously I have used 2.6 but this time in EPL there is a 2.7 ok now we can also check in Siebel - - version so here it will display yes it's a 2-point 7.0 this is the configuration file of the in Siebel which is used now let's clone the OpenShift NC belga trapa so here I'm just using the gate clone and it's cloning the open shaped and Siebel so open shift in Siebel git repo is managed by the open shaped open-source community and they have created a lot of the inventory files dynamic inventory files clay books and rolls and so on according to the version as well as in this video we are going to use a 3.9 so it will fetch all those branches so what you can do you can go there and check it so I'm going inside this folder then I'm fetching the latest and I'm checking out to release 3.9 because by default it will give you 3.1 oh I don't want to use 3.1 or because this is the latest and sometime buggy so I'm using 3.9 so I'm checking out in this branch yes now you can see git branch and you are in 3.9 ok this is ok now you need to generate the SSH keys on master so it should be without passphrase here so generated and I need to send this passphrase to my all the notes including master so you can see I'm sending yes hot spot of the master yes yes in front perfect let's verify this ones if I use your route ad master dark OpenShift example.com yes logged in if I do intra yes node one yes - yes perfect now we need to create the inventory file so what I can do I can go out from this location so you can see there are a couple of files and folders here you can see here there's inventory here and inside the inventory you have the dynamic inventories and you have the host specific entry enmities for the bluster affair asset so on so I'm not going to use these inventories I'm going to create my own so here we attained my inventory file file name could be anything in mint tea dot ini okay in this location and let me pick something yeah this is my master nodes YK it was his base this is the etcd database which is also running on the same node master and here I will explain this one little bit so don't confuse I'm just going to put the IP addresses okay yes so let me copy this inventory file from here up to here and I'm pasting yes let's go on top so this is the vest so we are enabling the debug level for I'm using the SSH user to connect is root then i'm using the excluder falls for the darker and open shape from the update means they will not be updated here the container rise this true means it will pull the images to run the parts for the like web console and but this freaking Seoul and so on so so this is the content rise environment this is the Sdn image which we are going to use it here so this is the Sdn software-defined Network and OpenShift is heavily based on the you know capacity of the nodes they have these specific requirements so if that requirement is not going to match your PlayBook will be failed so I am saying okay this availability should not be checked so whatever that is I have available it should be used by the OpenShift and also using the Taurus Taurus as you know darker can be configured on the separate partition or the volume or by use the overlays storage drivers so I'm just skipping that one as well from the check right area I am also disabling the check for memory availability and our query maize availability so these things will not be checked while running the prerequisite playbook so yeah I am you can say the ignoring these kind of check criteria here then yeah you can see here this is the limitations we are putting as per the standard of the open shaped one core can have the ten parts running by defaults if you want to tune it you can tune it here this is the pod per call so in a one core you can run ten parts by default this is the default functionality if you want to increase that one you can increase that one but remember it is not recommended in the production environment this is my testing so I can increase that one as well deployment here is that type is origin so you can mention here Enterprise if you have the you know subscription or the license from the radar to run the Enterprise version of open shipped so this time I am using the open source version of the open shift so this will be origin so deployment but will be also or is in here which version of the origin you are going to be used so this is the three point 9.0 packaged version is also three point 9.0 a maze version will also three point 9.0 so these are the versions okay cockpit is used by the poppin shift to provide the console registry and so on here I am dedicating my node so I mentioned here open shaped hosted router selected by default your router's is going to be hang up on masternodes so in my case I have the infrastructure node so I am saying routers will be created or placed in the reason infra so whatever the node I have in the infra reason my router will be placed there and same thing I have mentioned here for the registry here so registry will also go in the infra node so infra reason this is the subdomain name my domain name is open shape dot example.com so whatever the application you are going to create or launch in this openshift they will have the naming convention like your application name - your project name dot eps dot open shape dot example.com so whatever the subdomain name you want to use it here you can use accordingly it will be depend on your domain which you are using public host name this is the host name which we are going to use to access the dashboard so this is our public host name master dot open shape dot example.com I explained this one we are also hosting the registries a pod on the reason infra and a little bit down you can see here here this is my username by default open shape - dashboard you are going to use there is no username and password to login so we are using here HT passwd auth login method of provider and we are creating here one username is called demo and this is also the password demo which is the created in the Wrentham encoded string here right ok now I think we all good yeah a little bit up you get yeah oops oops oops oops I think we missed something ok yeah this one let me copy it again that's why I was looking why we had we don't have the information about notes okay ctrl C and paste it yeah yes here you can see this is my groups so this is the master nodes and etcd we are using your master dot open shape dot example.com this is the IP address of this particular machine this is the etcd so it is CD is also running on the master node and we have mentioned here this is the master so why we are using the master node inside in nodes because when you will configure or install the open shaped your Sdn should be means network connectivity for the open shift component will be done by the nodes and that is going to be configured the Sdn component on this so this is the necessary you have to also use your master inside your nodes and I am saying ok open shift schedule able is true if you are not using it by default master node cannot have any pod running and if the pod is not running on the master none of the pod or container will be you know allowed to be run there so this is the necessary this is the in front node which is also the schedule schedule able is true and here I am mentioning open shaped node label so this is called infra and will be in default zone so this is the intra and this is the infra a reason is defined inside our routers and registry so these parts will also go to this node so this is the thing which we have mentioned here okay I think everything is correct now once you have saved an exit now we have a one playbook which is called prerequisite so let's run this one this is available inside it so we are going to run it and we are passing our own inventory file here and let's see what it will say to you so this is the prerequisite playbook which we have ran here which is going to check all the nodes master in for our node 1 and node 2 and we'll give you the report these packages are already installed if the package is not installed here it will install those packages as well yeah so bait for the ten-second disabling the fireball D because cubed proxy or will I will say the proxy service which is going to route the traffic between the nodes the app nodes heavily based on the IP table so it is not going to use your fireball D I believe everything will be fine yeah so you can see the installer status is completed and everything is okay if there is some error it will display those errors here and you can resolve those errors and read on your prerequisite playbook so in my case everything is okay nothing to worry about it okay now our prerequisite is a passed you can see there is nothing is failed okay now we have to run the deploy cluster so I would recommend you to make your cluster deployment faster or quicker it will download couple of images from the repository so you can use these command this command docker pool you can pre pull your images yeah on the master node or on the rest of the node so I'm pulling you can see it will download the etcd it will download the open V switch it will download the nodes it will download the origin so yeah it will be very good if you can pull these images before running the deploy cluster ml playbook because it will make your cluster deployment faster these are the images are the size in the like and GB so it's some some some amazing sizes 1.6 or 1.8 gig so yeah it will be better you can download these images previously or you can directly run the deploy cluster playbook it will download those images on the run time so this is just my recommendation like you can pull these images fast and then run the deployment so it will make your deployment very quick so I have just I ran this one on my master node simultaneously you can see I can use this command to pull the images on my in front load yeah so this is Joker pull here on my node 1 and here also on my not 2 so I'm pulling all these images so it depend on you totally what way you want to follow you want to download these images during the cluster deployment or you want to pre pull these images before the deployment hmm so it will take time because as I mentioned the size of these images is the huge like in jeebies I think 1.6 or 1.8 gig you can check it here it also started here here and here yeah so we have to wait for the few minutes so until these are the images is going to be download on my system I'm going to pause this video because I will resume it once done okay so my image has been downloaded so you can see here this is my master node so what I can do I can just put here clear and darker images yeah so you can see some is one point four nine one point four six one point two six here as well yes clear you can see darker yes and here as well clear [Music] images okay darker images yes so till now all good so what I can do we can reach here now let's deploy the open shaped cluster so we have to run this one from the master node and I'm using this command n Sybil playbook this is my inventory file and this is the playbook to deploy the cluster when you press ENTER it will start deploying the open shaped cluster three point nine so if something is wrong you can troubleshoot it and rerun this playbook again I hope everything will be fine and our cluster will be deployed [Music] so as this time is installing the NTP because it's required to synchronize the time clock from the NTP server so you can watch this output which is produced by the NC Bell playbook and you can check if something is wrong what escaped what changed you can read out the clip file because they are using couple of rolls so I haven't described the playbook itself because I believe if you are deploying the open shaped cluster you have already the understanding about the in Siebel and playbook how to write and how to use the rules so if you go there inside the location where I have downloaded these play books from the open shipped in Siebel you can get the idea what the things is going on here so don't worry about some a red color output because if something is wrong miserly it will quit from that location so it's still our playbook is running so it means that that one which we have seen in red color was ignored so don't worry about it now it's saying okay start an enable master API so it's going to start the master node and it's trying to get the master API so yeah it is retrying those things so you need to just wait now it's trying to start an enable D master controller on master node actually we have used the continued rise environment inside our inventory file so what it's doing its running the part on the master node for the API and controller and once those thought has been any slice successfully and it started and start walking it will move to the next one there is another solution as well if you don't want to use the containerize environment so what you can do you can use the OS based cluster setup but as you know like in openshift environment we can use our our HCl or we can use the atomic host so containerized environment is necessary for the atomic host if you are using the OS like RHEL yeah you can use the containerized as well as the OS specific there is a something wrong here which we can see unable to start service this job this because the control process exit with error core this this this ok so something is wrong here you can check it this systemctl status so we need to check it here what wrong and why master and it was failed in master Cheney ok let me check it here fail to start atomic open shift master invalid this invalid value this ok let me check what the invalid value could not read the file this one no such file no such file okay an invalid argument as well [Music] monster monster dota TC TC Z or T could not read this file there is no file so let me verify this one yes this file is not available it was mr. doherty tcd desk c8 or CRT mustard he's also there but there is no certificate Wow strange okay let me rerun this play poker game hmm yeah some beard says okay it is a source [Music] could not find the requested service origin/master okay what we can do let me open the another terminal as a such route at master hospitai is this and here darker PS etcd is running we'll see get thoughts this service is not running yet so okay hmm unable to restart origin master API the same error why it is not going to use this one able to restore service this one origin master so if I do this one here systemctl restart let me check the status so it says okay - L there is something wrong here invalid configuration master - config dot EMM and here it's saying this is slash et Cie origin master master - it is idiot - see a door CRT can I check my inventory file once again in event we thought I and I and I believe let me check here cat so that's C host file here 192 168 0.131 infra heads 1 3 2 1 3 3 + 1 3 4 ok ifconfig so it has 190 168 0.131 this is similar to this one 3 1 okay inventory ini master taught open shaped at example.com 191 six eight zero dot 1 3 1 this is my 80 CD 191 680 2.1 this is the master 191 60.1 infra 1 91602 1 3 2 this is node 1 181 say it 1.13 3 and this is 1 3 4 [Music] provider is okay this is my password and if I use this command hmm invalid master can take this file so master server one shift master dot c RT c-- a dot c RT TC server dot c RT so which one is looking by here master taught etcd - see a dot c RT this is the TCD server this is it is it a client I believe it's not this one let me check no such container origin master controller okay everything is rope-like correct let me tableau sure this issue and I will resume my recording once it is done yes I have found one bug here previously I were using the NC bill was in 2.7 and somewhere I found a small bug in 2.7 with etcd database and certificate so I have ran this command to downgrade it my in Siebel and as of now I am using ansible test - person so you can check it here this time I'm using 2.4 so you can just like go back one previous version 2.6 but in my repo I have 2.4 I believe this will fix this issue so you can rerun this playbook again so I'm just using this deploy cluster I believe this time it will deploy the oops oops oops oops oops oops I'd say it's current NC bill words and this is not supported supported version to point this odd newer ok so this time I am getting another one so yeah update NC bow so if I do this one I believe in my rep oh I don't have 2.4 is available in extra ok and if I do this one I hope I [Music] don't know this is the version is available now so let me download this one I'm just pausing this video again hello friends I'm back I have double shooted this issue so this time I'm using the in civil war zone is two point six point six so I believe this time it should run so let's run this playbook this is the deploy cluster so I believe this time you will not get that issue if it still is issue it means somewhere is the problem in clay book so I will troubleshoot that one father mmm previously it was saying something days I yes you can see this time it has been created it mean that was the issue with n Siebel version 2.7 point O is not compatible so don't use this one use 2.6 could be six point two point six point oh two point six point one two three whatever so don't use two point seven point Oh yeah it's past it's doing some other stuff it was failed on the previous step here somewhere here or controller and after this one it was failed but this time it passed now it's restarting the master controller I believe this time it will deploy your open shaped cluster so until this deployment is going on so let me revise what the agenda is still remain to do so yeah I have displayed the setup for the 4:00 p.m. what the infrastructure I have builded on my BM beer worker station then I have downloaded the open shift and Sybil kit rep oh yeah and created our own inventory file I explained this one as well they'll run the prerequisite yes we done that one part now this is so step number v is going on once your open shift cluster is deployed we will create the admin user fast because by default there is only the system username is admin you can use that user to administrate your open shipped environment but from or only from the master node not from the web console or not from the other nodes where you have installed OC client so we will create the admin user with the admin privileges then we'll create the project then we will create application in that project and we will access this one so it still six seven eight and nine is remain to do so waiting for thee installation II we have not customized this playbook so it's going to use all those possible tasks or plays which is mentioned here so like for example NFS I scuzzy stories yeah so if you want you can customize these clay books according to your need and you can save your time of the deployment so if I check it here till now no record so yeah only one note is there which is master dot OpenShift at example.com ready there is no rule one minute ago and this is the kubernetes version they are using 1.9 Wow so master is set up now he's going to set up your infra and note 1 note2 you can check it here how I'm able to run this OC command so you can see OC gab not get OC Who am I so it will say you are the system admin so you can run these commands only from this master node but if I want to run this OC client command from somewhere else maybe from like node 1 node 2 infra or from my personal laptop so how you will login so you need to create a user account with the admin privileges then you can administrate your open ship from the remote location or maybe from the web console so we will do that one yeah you can see here you see get notes so here is my intro this is the master this is the node 1 this is the note tool but rule is rules is still none so yeah beating to assign the rules I believe till now there is no pod yes there is no pod is running so we should have couple of parts as we have chosen to run in a containerized environment so you can see here node labels they have defined the labels so here the master node label has been changed yeah so need to fetch the information further let's run this command not this one nodes yes you can see this is the master this is the compute so none means none of the role has been specified this one because we have chosen this one is a in front so only for the registry and routers parts will be running from this node so the rules has been defined now let's see yes fetch the docker registry uproot it's setting up some registry certificate and so on port services almost is going to finish yes you can see here registry deploy this is registry container creating and this one router has been deployed this one if I do this one again yes running running running and it's still this one is creating so deploy and creating so this will be your final I believe yes you can see yeah you can you you will have two parts one is registry and one is router so where these two parts are running so you can use here - Oh wide so you can get the further see dhaka registry is running on intra and a router is also running on intra so yes because in our playbook we have mentioned to run the registry and routers on in front note because intra reason we have chosen as a selector to run these parts yes you can see it's creating I believe almost is done verifying the console is running okay and here if you see still is creating this one there is also option W means wait until is going to create here and this is going to be run on master okay this container creating so just wait for thee okay you can see failed zero zero zero zero nothing is failed completed web console install completed everything is perfect Wow okay so now you can see everything is running so your OpenShift arisen 3.9 cluster has been deployed so we have reached up to take the step now we need to create a user account so here you can check it once this this this this okay now this is the particular file we are using see here and if you are trying to read this file you will see the demo user which we have passed in our inventory file this is the user and this is the password demo demo now I would like to add another user inside it and the user name is called admin so you require HT possibility command so let me use this one and I'm adding this one new user this and password this like to read this file and you can see you have two users now we need to assign the admin cluster admin role to this admin user so you can check Oh see Who am I so you are a system admin use this command OC a DM policy ad cluster role to user and this is the role name and this is the user name yes now you can see you are assigned to this one let's verify this one OC login so I can use hero see login by default it will go to this location username is admin password is and loving successful let's see who am I now it will say admin you are not the system admin right cool now what you can do let's try to open so I'm just going to use here VI m /e TC host file and you can see here yes I have also read stirred my host name here because I don't have the DNS so let me open and run here HTT P colon double slash master dot OpenShift example.com : 8 4 4 3 oops HTTP yes now advanced go to this because this is the self signed certificate Wow login here as admin password login this is your open shift let's create a one project name is supposed demo demo demo create demo has been created go here browse you can run a simple application in PHP for example next latest application name is suppose demo test our demo app for example demo app 1 now from where you want to get the repository for the PHP ma so I believe I have this you can download my report and then click on create close click on overview you are inside the demo and you can see build has been triggered and here you will see it will display the logs yeah you can see this is the application name if I hope you remember this one I have mentioned my subdomain name is apps open shape dot example.com so this is the external root or the traffic to get the access of this application so how this is the naming convention is this is your application name demo app 1 - this is the project name dot this is your subdomain name which you mentioned inside the playbook to deploy the cluster so this is your subdomain so whenever you are going to launch any application here all those applications will be the part of apps dot open shaped or example.com so this is the build has been triggered it will clone the repository from the github and then it will run a one pod here so we need to wait for maybe one or two minutes yeah you can see it's fetching and now it's pushing into the open shipped internal registry I believe you know this concept is called source to a maze as to I this is the image name and tag name so this is demos last demo app 1 : latest this is the image which is pushed in your OpenShift internal registry yes you can see and now here it's running the pod so by default right now it's 0 parts from this so just paid for a movement it will have a one pod running yes now you can see the one pod is running and this is the URL this part is running there so when you click on it you will see this part is running on no two dot open shape dot example.com if you want to verify the same from here you can verify let me come to here OC get parts ok and here you can oh that part is running in the demo so you can use here demo see the build has been completed and there is a one part which is running on here right here there is a one more thing I would like to demonstrate you can see RC I believe you know the concept about the assi I don't want to use here like you can see desired one means you required only one part so it will always run the one part so how you will access this application so as I mentioned we have the infrastructure node here and our router is also running so this is my laptop how I will access this application so I will access that at that application by using the infra node so as I don't have the DNS so what I will do I will use the EDC host file and here this is my in preneur let me copy and Here I am just sorry oops sorry I'm just pasting here oh I'm just pasting here and I need to mention the IP address sorry uh the host name is over here so let me copy and paste it here just remove HTTP right and save it why I'm mentioning here 132 because this is the IP address of my infant node where our router is running so a router will route the traffic to reach to this application then and now just stick here Wow you can see this is the application is running and as of now there is only one part so what you can do you can just click on this tree scalar now it's creating you can see two pods pod pod come on yeah this stool is creating and this is running so it is creating another one you can see yeah both are running so you can come here you can see two parts so this is running this is also running let's see the information they are running there you can see one is running on this one is built completed this one is running on order two and this is running on node one yes and now the desired state of this one is to write this one so this is the wave which you can use if you want to scale it down so you can do this one from here oh see edit are see this one - n demo I believe yes and here let go down and you can see here replica - so just you mention here one save and close that's it now you can see desired - current - ready one let me check it again just wait I'll check we'll see get dizzy - and demo okay OC add it DC this one oops here - demo yes here deployments just mention here one save and close yes desired one current one and let me check the RC as well yes and now if you check your thoughts see here only one running part and let me check here yes one running part so both way you can manage you can do this one from the graphical consoler you can do this one from the CLI so let's check these endure whatever I have mentioned so we have created a one admin user account okay we have project by using the web console yes deployed an application and we have accessed the application using the URL and we have used the TC host file to resolve the host names because I don't have the DNS running so I hope you enjoy this video in next video I will try to configure DNS I don't want to use these lessee TC host file because we have we are going to run multiple containers are parts here so it's very hard to you know resolve the hostname so yeah we will create the DNS with wildcard entry for the Apps dot open shape dot example.com so whenever you are going to run the pod inside it it will automatically resolve those host names or the URLs there are a couple of things in my next videos like I will configure the persistent storage for the registry by using the NFS and some shared stories then some cluster operations s2i source to emails and so on so I will publish those videos soon I hope you like this video and thank you please give the comments how you liked this video and so on so you're most welcome thank you thank you so much have a nice day to you guys

Channel: Suresh Chandra

Views: 14,426

Rating: 5 out of 5

Keywords:

Id: JhlzSoayksY

Length: 89min 17sec (5357 seconds)

Published: Fri Oct 26 2018