Creating an OKE Cluster

1. In the Compute Cloud@Customer Console navigation menu, click Containers, then click Kubernetes Clusters.

2. On the clusters list page, click Create Cluster.

3. In the Create Cluster dialog box, provide the following information:

   • Name: Enter a name for the new cluster. Avoid entering confidential information.

   • Compartment: Select the compartment in which to create the new cluster.

   • Kubernetes Version: Select the version of Kubernetes to run on the control plane nodes. Accept the default version or select a different version.

     If the Kubernetes version that you want to use isn't listed, use the CLI or the API to create the cluster and specify the Kubernetes version.

   • Tagging: Add the following free-form tags for the cluster resource.

     Note
     
     

     Don't specify values for the OraclePCA-OKE.cluster_id defined tag or for the ClusterResourceIdentifier free-form tag. These tag values are system-generated and only applied to nodes (instances), not to the cluster resource.

     Use OraclePCA defined tags to provide the following information for control plane nodes. If these tags aren't listed in the Compute Cloud@Customer Console Tagging menus, you must create them. See Create OraclePCA Tags For OKE.

     Note
     
     

     None of these values - SSH key, number of nodes, node shape, or node shape configuration - can be set or changed after the cluster is created. If you set these tags when you update the cluster, the new values are ignored.

     • Your public SSH key.

       Specify sshkey for the tag key (OraclePCA.sshkey). Paste your public SSH key into the Value field.

       Important
       
       

       You can't add an SSH key after the cluster is created.

     • Number of nodes.

       By default, the number of nodes in the control plane is 3. You can specify 1, 3, or 5 nodes. To specify the number of control plane nodes, specify cp_node_count for the tag key (OraclePCA.cpNodeCount), and select 1, 3, or 5 in the Value field.

     • Node shape.

       Specify a shape such as VM.PCAStandard.E5.Flex.

     • Node shape configuration.

       You can change the default shape configuration.

       To provide shape configuration information, specify cp_node_shape_config for the tag key (OraclePCA.cpNodeShapeConfig). You must specify the number of OCPUs (ocpus) you want. You can optionally specify the total amount of memory you want (memoryInGBs). The default value for gigabytes of memory is 16 times the number you specify for OCPUs.

       Note
       
       

       If the cluster will have 1-10 worker nodes, specify at least 16 GB memory. If the cluster will have 11-128 worker nodes, specify at least 2 OCPUs and 32 GB memory. You can't change the number of OCPUs or amount of memory when you update the cluster.

       In the Value field for the tag, enter the node shape configuration value as shown in the following examples.

       In the following example, the default amount of memory is be configured:

       {"ocpus":1}

       In the following example, the amount of memory is specified:

       {"ocpus":2, "memoryInGBs":48}

       Note
       
       

       If you use Terraform to specify a complex value (a value that's a key/value pair), then you must escape the double quotation marks in the value as shown in the following example:

       "OraclePCA.cpNodeShapeConfig"="{\"ocpus\":2,\"memoryInGBs\":48}"

   • Add-ons: This section shows a tile for each add-on that's available for this cluster. In the Create Cluster dialog box, all add-ons are Disabled. See Installing the WebLogic Kubernetes Operator Add-on.

4. Click Next.

5. On the Network page in the Create Cluster dialog box, provide the following information:

   • Network Type. Specifies how pods running on nodes in the cluster communicate with each other, with the cluster's control plane nodes, with pods on other clusters, with other services (such as storage services), and with the internet.

     The Flannel Overlay network type encapsulates communication between pods in the Flannel Overlay network. The Flannel Overlay network is a simple private overlay virtual network that satisfies the requirements of the OKE networking model by attaching IP addresses to containers. The pods in the private overlay network are only accessible from other pods in the same cluster. For more description, see Creating Flannel Overlay Network Resources.

   • VCN-Native Pod Networking connects nodes in a Kubernetes cluster to pod subnets in the OKE VCN. As a result, pod IP addresses within the OKE VCN are directly routable from other VCNs that are connected (peered) to the OKE VCN, and from on-premises networks. For more description, see Creating VCN-Native Pod Network Resources.

     Note
     
     

     If you specify VCN-Native Pod Networking, then the VCN you specify must have a subnet named pod. See Creating VCN-Native Pod Network Resources.

   • VCN. Select the VCN that has the configuration of the "oke_vcn" VCN described in Creating a VCN (Flannel Overlay) or Creating a VCN (VCN-Native Pod).

   • Kubernetes Service LB Subnet. The subnet that's configured to host the load balancer in a Kubernetes cluster. To create a public cluster, create and specify here the public version of the "service-lb" subnet described in Creating a Worker Load Balancer Subnet (Flannel Overlay) or Creating a Worker Load Balancer Subnet (VCN-Native Pod). To create a private cluster, create and specify here the private version of the "service-lb" subnet.

   • Kubernetes API Endpoint Subnet. The regional subnet in which to place the cluster endpoint. To create a public cluster, create and specify here the public version of the "control-plane-endpoint" subnet described in Creating an OKE Control Plane Subnet (Flannel Overlay) or Creating a Control Plane Subnet (VCN-Native Pod). To create a private cluster, create and specify here the private version of the "control-plane-endpoint" subnet.

   • Kubernetes Service CIDR Block. (Optional) The default value is 10.96.0.0/16.

   • Pods CIDR Block. (Optional) The default value is 10.244.0.0/16.

   • Network Security Group. If you check the box to enable network security groups, click Add Network Security Group and select an NSG from the drop-down list. You might need to change the compartment to find the NSG you want.

6. Click Next.

7. On the Node Pool page, select the Add Node Pool button to optionally add a node pool as part of creating this cluster. See Creating an OKE Worker Node Pool to add node pools after the cluster is created.

   If you select the Add Node Pool button, enter the following information in the Add Node Pool section:

   • Name: The name of the new node pool. Avoid using confidential information.

   • Compartment: The compartment in which to create the new node pool.

   • Node Count: Enter the number of nodes you want in this node pool. The default is 0. The maximum number is 128 per cluster, which can be distributed across multiple node pools.

   • See Creating an OKE Worker Node Pool for information about Network Security Groups, Placement Configuration, Source Image, Shape, and Pod Communication.

8. Review your entries.

   If you created a node pool, you have the opportunity to edit or delete the node pool in this review.

9. Select Submit.

   The details page for the cluster is displayed. Scroll to the Resources section and select Work Requests to see the progress of the cluster creation. If you created a node pool, the NODEPOOL_CREATE work request might still be In Progress for a time after the cluster is Active and the CLUSTER_CREATE work request is Succeeded.

   Under Resources, click Work Requests to see the progress of the cluster creation.

   The cluster details page doesn't list OraclePCA tags on the Tags tab (and you can't filter a list of clusters by the values of OraclePCA tags). To review the settings of the OraclePCA tags, use the CLI.

   The cluster details page doesn't list the cluster control plane nodes. To view the control plane nodes, view the list of instances in the compartment where you created this cluster. Names of control plane nodes are in the following format:

   oke-ID1-control-plane-ID2
                  

   • ID1 - The first 32 characters after the ccc_name is the cluster OCID.

   • ID2 - A unique identifier added when the cluster has more than one control plane node.

   Search for the instances in the list whose names contain the ID1 string from this cluster OCID.

What's Next: