Welcome to our demo on Container Engine for Kubernetes is also referred to as OKE. Let's see it in action. I'm logged onto my Oracle Cloud Account here, and to bring up Container Engine for Kubernetes click on the navigation menu on the left-hand side, and then click on Developer Services, and under Developer Services there are various services which are listed including Containers and artifacts, APIs management, DevOps, Resource Manager, etc. OKE is found under Containers and artifacts and you can see the first link on OKE here. The first thing you notice here is when I click on OKE, it's asking me to create a cluster. It says no cluster exists. If I click on "Create cluster", we have simplified the process of creating a cluster here. So you can see here that there is an option for Quick create and then there is an option for Custom create. If I click on Quick create, I can see that it provides an option to create a new cluster along with creating new network resources. New network resources include, indeed all the details, one regional subnet and all the details are available here. There's also something called Custom create, and if you click on that, you can see some options for custom create. In this one, the big difference is you already have an existing network resource to use, so it uses that and then you can use the network to create your cluster. We'll go with a quick create because we want to create a new network to be used for my cluster here. I'll click on Launch workflow, and what this will do is it would bring up a workflow to create a cluster. First thing I'm going to do is I'm going to put a name. It's asking for a compartment. We can choose a Kubernetes version here. I'm going to choose the latest one, and then there is a Kubernetes API endpoint. This is the type of access to the clusters Kubernetes API endpoint. It can either be private, which means it could be accessible by other subnets in division, or it could be public, which means that it's accessible directly from the Internet. We're going to choose public here. Then there is Kubernetes worker nodes, and it's either private or public. Private basically means that the worker nodes will be hosted in a private subnet, public basically means that nodes are created will be hosted in a public subnet. Now for this example, we're not going to SSH into any of these worker nodes. I'll leave it as private. If you need to do that, if you need to SSH, you would use public workers, or you could use private workers, worker nodes in a private subnet, but you would read a bastion host or a bastion server to SSH into this machine. That's a more advanced topic. Right here, I can choose my shape, and you can see here it's basically different options which I have available. This is basically the number of CPUs and the memory I want my worker nodes to have. Then below here, it gives me the number of nodes in the node pool which I want to create. By default it's picking up three. I could have chosen this to be a different number, and then you have some more options on, you can customize the boot volume, etc. There's one which is called image verification here. This option basically gives you a choice whether to only allow the deployment of images from OCI Registry that have been signed by particular master encryption keys. If you choose this option, you have to specify the encryption key and the vault that contains it. You can see here. I'm just going to skip this one, and then again, this is SSH keys. If my worker nodes were in a public subnet, you need to provide an SSH key here. If you don't provide an SSH key, you will not be able to connect to the worker node using SSH. Anyway, these are advanced features. We're going to skip them. Then right here, I can create my cluster, so click on "Create cluster", and this process generally would take a few minutes. Once the cluster would be up and running, I would come back here and then we'll try to access the cluster. It's doing a check right now. You can see it's creating virtual cloud network. It's creating node pool, etc. If I close here and I go back to the screen here, you can see that the cluster is getting created and you can see all the details here. It gives me the Kubernetes API endpoint, etc. If I look at node pools, I can see that there is one node pool getting created with three worker nodes and it's waiting for the cluster to get created. Let me hit pause here. Once this is up and running, we will resume the demo. That process took a few minutes, and as you can see here, my node pool is active and the cluster is set up. If I see here, I can click and I can see that we have a total of three worker nodes and one worker node has failed to create. You can see here because it gives me out of host capacity. This can happen because I'm running a free trial account, so I have a few service limits. Just make sure that if you're creating a cluster with a specific number of worker nodes, you have the requisite capacity, but it's totally fine. You might actually get a situation like this. You can see here worker request, and you can see some which have failed and one which is in action, etc. If I go back to my cluster, I can get more information. Node pool is here. You can see the total worker node is actually two, and there are some other features like image verification, which we actually didn't enable when we spun up this cluster. There's also this thing called Quick Start. You can access your cluster right from Cloud Shell, and that's a very good feature because you don't have to do any local setup. To do that, you can click on access cluster here, and it gives you a couple of options. You could access the cluster through Cloud Shell or you could access it locally, like I said. But to do it through Cloud Shell just makes life a bit easier. To do it click on Launch Cloud Shell here, and then there is a kubeconfig file which needs to be configured in order to access your cluster, and it also gives you a command to do that, so copy this and then you can run this in Cloud Shell, and hit Enter. You can see here that if I'm running it for the first time, it would create this kubeconfig file, but I have run this earlier, so it says that there was already a kubeconfig file found here, and the new config file has been merged into it. If you want to just see what this kubeconfig file looks like, just pop it this location. Right here you can see all the details on the kubeconfig file, and it's again a foundational course, so we're not going to go into details here. But it has information on the cluster, the cluster endpoint, and so on and so forth. It gives you some more details on the configuration for this cluster. Now let's go ahead and run some basic commands. If I say, get me nodes, you can see that I have two nodes running here, and I can see those nodes. If I say, get me the parts which are running on those nodes, you will see there are no parts created because we have not applied any service yet. We could go ahead and deploy our application here and start using this cluster. This was a quick demo on how you can create an OKE cluster. I hope you found this demo useful. Thanks for your time.
