Create OKE Clusters Running on OCI

Add Oracle Container Engine for Kubernetes self-managed clusters running on OCI to your multicluster environment

Before you begin

You’ll need to:

  • Set up an Oracle Cloud Infrastructure (OCI) account with
  • Generate an SSH key pair to use for cluster authentication

Create a new OKE cluster on OCI

To provision new Oracle Container Engine for Kubernetes (OKE) managed clusters on OCI, complete the following steps:

  1. Log in to the console. To find the console URL for your cluster, refer to Get console URLs and use the rancherURL value.

  2. Open the navigation menu and select Cluster Management.

  3. From the left menu, select Cloud Credentials, and then click Create. Cloud credentials store the credentials for your cloud infrastructure provider.

  4. Choose Oracle.

  5. Provide a name for the cloud credential and then fill in the rest of the fields with information from your OCI account and its API signing key.

  6. From the left menu, select Clusters, and then click Create.

  7. Select Oracle OKE and provide a name for the cluster. Do not select Oracle OKE (Legacy).

  8. Expand Member Roles to add any users that you want grant access to this cluster and their permissions.

  9. Expand Labels and Annotations to configure Kubernetes labels and annotations for the cluster.

  10. Select the cloud credentials that you created. Ensure that the appropriate Region and Compartment are selected from their drop-down menus.

  11. Click Next.

  12. Set up your network. Choose Quick Create to create a new virtual cloud network (VCN) configured to the specifications required for an OKE cluster or Existing Infrastructure to use a VCN that’s already configured in your OCI account.

    • If you choose the Existing Infrastructure option, then select the compartment where your VCN is located from the VCN Compartment drop-down menu, then the VCN itself from the Virtual Cloud Network drop-down menu. Next, select subnets within the VCN for each of the Cloud Plane Subnet, Load Balancer Subnet, and Worker Node Subnet drop-down menus. See Configure a VCN in OCI for requirements.

    • The VCN compartment does not need to match the compartment specified in the cloud credential.

  13. Click Next.

  14. Configure the cluster control plane. Select an OKE Version and then a CNI Type.

  15. Choose a Node Image from the drop-down menu.

  16. Copy or upload an SSH public key to manage authentication of the cluster. Your SSH public key is installed on the cluster nodes, enabling SSH after the cluster is created.

  17. Add node pools to your cluster. Clusters without node pools will schedule pods on control plane nodes.

  18. (Optional) Install Verrazzano on the cluster. Choose a Verrazzano version from the drop-down menu. You can also expand Advanced to make changes to the Verrazzano Resource YAML. By default, Verrazzano is installed using the managed-cluster profile which enables a limited set of components on the cluster.

  19. Expand Advanced Settings to make additional modifications to the default settings of your new cluster.

    • YAML Manifests: Supply additional YAML manifests that are automatically installed after cluster creation. The total size of all additional YAML manifests may not exceed 500 KB.
    • Cluster Networking: Configure cluster IP ranges and proxy settings.
    • Container Registry: Specify a private registry for your container.
  20. Click Create. It can take up to 30 minutes to provision all of the resources for your cluster, particularly for multi-node clusters.

When your cluster finishes provisioning, you can access it from the main Cluster Management page.

For help troubleshooting cluster creation, see Cluster Creation Issues.