Welcome back. When working with Oracle Container Engine for Kubernetes, you can leverage OCI tagging to add metadata to cluster resources. Tags are used to organize and locate resources based on your business needs. Then what are your tagging options? First, the cluster resource itself can be described using what are more tags. Then as you create each node pool, you can define node pool tags. For the nodes that are added to the node pool, you can choose to have them simply inherit the node pool tags or create node tags that will be applied for each provisioned instance. For block volumes, you can choose to have them inherit the cluster tags or defined initial block volume tags that will be applied to each block volume when it is created by a Kubernetes persistent volume claim in the cluster. In a similar manner, you can choose to have load balancers inherit the cluster tags as well or define initial load balancer tags to be applied when they are created by load balancer or Kubernetes service deployments in the cluster. As a reminder, the OCI tagging service provides two ways for you to add tags to resources. Tag administrators can first create defined tags that specify value choices in advance. Then users such as OKE cluster administrator can apply those defined tags, or add free-form tags to provide other metadata to be applied as well. You'll find tagging useful for various use cases such as resource tracking, for example, to report all OCI resources like compute instances, load balancers, and block volumes that are associated with a Kubernetes cluster, or you may wish to apply application specific tags to load balancers and block volumes in order to track resources for a given application running in a cluster. Other use cases involve grouping authorizations for identity and access management policies. For example, to authorize worker nodes to access a designated objects storage bucket using instance principles for those nodes as part of a node pool dynamic group tag. A cost tracking example would be to obtain detailed cost reports for the running of Kubernetes clusters categorized by application, or by line of business. Let's now take a quick look as to how tags can be applied to various resource types using the custom create wizard. Let's navigate over to developer services and OKE, and we'll look at creating a new cluster using the custom create wizard. When you launch the workflow side for the normal setups you can do, right underneath at the beginning under advanced options, is where you have the option to come down and add either cluster tags, and/or initial load balancer tags, and/or initial block volume tags. You can add one or more in each of these sections. For example, if I had a particular tag namespace that was a defined tag already in place, I'm going to take a look at bill codes and there're some options here we're going to just give that a value. I can add another one. Let's do something with finance namespace, and there's a cost center, and we have an option as to which one that applies to. Then we could even add free-form tags as well. Maybe there's a DevTeam involved that wants to identify this resource, and we'll add that in place. You can add one or more tags in each of these sections as you see fit. Let's press on and show what would be involved in with the node pool. Let me quickly update these values, so I can get to the next screen. Here's my node pool and after you define your node pool down at the bottom, under advanced options is where you have both node pool tags that you can define for the pool itself as well as specific node instance tags that you could apply to those nodes. Now, you don't have to necessarily do this at cluster creation time. You can also do it to an existing cluster. If I look at my cluster that's already defined and click on the ''Cluster tags tab", that's where I can add cluster resource tags, there's the initial load balancer tags, that's where I can add those for the load balancers, and there's the one for block volumes as well. If you want to modify node pools, simply go to node pools, select the "Pool", and once again, you have two tabs, one for node pool tabs that you can add, and one for the node tags themselves in this area. However, you're not limited to just using the OCI console. For example, when creating a cluster with the OCI command line interface, you can add one or more defined, or free-form tags as shown here in this example. The same is true when you're creating node pools in the cluster. You can apply those node pool tags as shown here in this example, or as part of that same create command, you can instead choose to define node level tags as shown here, or even decide to add other tags to be applied to the node instances when they are provisioned. When creating the cluster with the CLI, these service-lb properties are used for defining the initial load balancer tags as shown in this example. Likewise, these persistent-volume properties can also be added to define the initial tags for block volumes that are created as a persistent-volume claim within the cluster. Finally, regardless of whether you provisioned your OKE cluster using the CLI or the custom create wizard in the console, the initial tags for block volumes can be overridden when they are provisioned as a persistent volume claim in the cluster. You do this by using the override parameters in the manifest file for that storage class definition as shown in this example. Likewise, when deploying a new Kubernetes service of type load balancer to your cluster, you can edit the manifest file to override values for both defined and free-form tags as shown here. That's it for this lesson on leveraging OCI tagging for your cluster resources in OKE. Thanks for watching.
