Running Ubuntu on Worker Nodes Using Custom Images

Creating a cloud-init script for managed nodes

To create a cloud-init script to run Ubuntu on managed nodes:

1. Create a new cloud-init script file from scratch with a filetype supported by cloud-init (such as .yaml), and add the following logic to the script file:

   #cloud-config
   apt:
    sources:
      oke-node: {source: 'deb [trusted=yes] <download-url>}
   packages:                                                       
    - <oci-package-name>
   runcmd:
    - oke bootstrap

   where:

   • <download-url> is the URL from which to download the Ubuntu node package that you constructed in the previous step (see Step 2: Construct the URL from which to download an Ubuntu node package). For example, https://objectstorage.us-sanjose-1.oraclecloud.com/p/45eOeErEDZqPGiymXZwpeebCNb5lnwzkcQIhtVf6iOF44eet_efdePaF7T8agNYq/n/odx-oke/b/okn-repositories-private/o/prod/ubuntu-jammy/kubernetes-1.29 stable main
   • <oci-package-name> is one of the following, according to the version of Kubernetes that you want to run on the managed node:
     • oci-oke-node-all-1.27.10
     • oci-oke-node-all-1.28.10
     • oci-oke-node-all-1.29.1

     The Kubernetes minor version must match the Kubernetes minor version you specified when constructing the download URL (see Step 2: Construct the URL from which to download an Ubuntu node package).

   For example, if you want to run Ubuntu 22.04 (jammy) and Kubernetes version 1.29.1 on managed nodes, add the following logic to the script file:

   #cloud-config
   apt:
    sources:
      oke-node: {source: 'deb [trusted=yes] https://objectstorage.us-sanjose-1.oraclecloud.com/p/45eOeErEDZqPGiymXZwpeebCNb5lnwzkcQIhtVf6iOF44eet_efdePaF7T8agNYq/n/odx-oke/b/okn-repositories-private/o/prod/ubuntu-jammy/kubernetes-1.29 stable main}
   packages:                                                       
    - oci-oke-node-all-1.29.1
   runcmd:
    - oke bootstrap

2. Save the cloud-init script file.

Creating a cloud-init script for self-managed nodes

To create a cloud-init script to run Ubuntu on self-managed nodes:

1. Follow the instructions in Creating Cloud-init Scripts for Self-managed Nodes to obtain the Kubernetes API private endpoint of the enhanced cluster to which you want to add the self-managed node, using the Console or the CLI.
2. Follow the instructions in Creating Cloud-init Scripts for Self-managed Nodes to obtain the cluster's base64-encoded CA certificate from the cluster's kubeconfig file, using the Console or the CLI.
3. Create a new cloud-init script file from scratch with a filetype supported by cloud-init (such as .yaml), and add the following logic to the script file:

   #cloud-config
   apt:
    sources:
      oke-node: {source: 'deb [trusted=yes] <download-url>}
   packages:
    - <oci-package-name>
   write_files:
   - path: /etc/oke/oke-apiserver
    permissions: '0644'
    content: <cluster-endpoint>
   - encoding: b64
    path: /etc/kubernetes/ca.crt
    permissions: '0644'
    content: <base64-encoded-certificate>
   runcmd:
     - oke bootstrap --ca <base64-encoded-certificate> --apiserver-host <cluster-endpoint>

   where:

   • <download-url> is the URL from which to download the Ubuntu node package that you constructed in the previous step (see Step 2: Construct the URL from which to download an Ubuntu node package). For example, https://objectstorage.us-sanjose-1.oraclecloud.com/p/45eOeErEDZqPGiymXZwpeebCNb5lnwzkcQIhtVf6iOF44eet_efdePaF7T8agNYq/n/odx-oke/b/okn-repositories-private/o/prod/ubuntu-jammy/kubernetes-1.29 stable main

   • <oci-package-name> is one of the following, according to the version of Kubernetes that you want to run on the self-managed node:

     • oci-oke-node-all-1.27.10
     • oci-oke-node-all-1.28.10
     • oci-oke-node-all-1.29.1

     The Kubernetes minor version must match the Kubernetes minor version you specified when constructing the download URL (see Step 2: Construct the URL from which to download an Ubuntu node package).

   • <cluster-endpoint> is the IP address of the cluster's Kubernetes API endpoint that you obtained earlier.
   • <base64-encoded-certificate> is the cluster's base64-encoded CA certificate that you obtained earlier (starting with the characters LS0t).

   For example, if you want to run Ubuntu 22.04 (Jammy) and Kubernetes version 1.29.1 on a self-managed node, add the following logic to the script file:

   #cloud-config
   apt:
    sources:
      oke-node: {source: 'deb [trusted=yes] https://objectstorage.us-sanjose-1.oraclecloud.com/p/45eOeErEDZqPGiymXZwpeebCNb5lnwzkcQIhtVf6iOF44eet_efdePaF7T8agNYq/n/odx-oke/b/okn-repositories-private/o/prod/ubuntu-jammy/kubernetes-1.29 stable main}
   packages:
    - oci-oke-node-all-1.29.1
   write_files:
   - path: /etc/oke/oke-apiserver
    permissions: '0644'
    content: 10.114.0.5
   - encoding: b64
    path: /etc/kubernetes/ca.crt
    permissions: '0644'
    content: LS0tLS1...LS0tCg==
   runcmd:
     - oke bootstrap --ca LS0tLS1...LS0tCg== --apiserver-host 10.114.0.5

4. Save the cloud-init script file.

Adding Ubuntu worker nodes as managed nodes

To add managed nodes running Ubuntu in an existing cluster

1. Open a command prompt and use the oci ce node-pool create to create a new node pool.
2. As well as the mandatory parameters required by the command:
   1. Include the --node-image-id parameter, and specify the OCID of the custom image that you created in Step 1: Create a custom image based on an existing compute instance running the required Ubuntu release.
   2. Include the --node-metadata parameter and specify the cloud-init script that you created for managed nodes in Step 3: Create a cloud-init script to install the Ubuntu node package and bootstrap the worker node, in the appropriate format for your environment:
      • Linux: --node-metadata '{"user_data": "'$(cat <cloud-init-file> | base64 -w 0)'"}'
      • Mac: --node-metadata '{"user_data": "'$(cat <cloud-init-file> | base64- b 0)'"}'
      where:

      • <cloud-init-file> is the name of the cloud-init file that you created
      • base64 specifies the file is to be base64-encoded

   For example, you might enter the following command on a Mac work station:

   oci ce node-pool create \
   --cluster-id ocid1.cluster.oc1.iad.aaaa______m4w \
   --name my-ubuntu-nodepool \
   --node-image-id ocid1.image.oc1.iad.aaaa______zpq \
   --compartment-id ocid1.tenancy.oc1..aaa______q4a \
   --kubernetes-version v1.29.1 \
   --node-shape VM.Standard2.1 \
   --placement-configs "[{\"availabilityDomain\":\"PKGK:US-ASHBURN-AD-1\", \"subnetId\":\"ocid1.subnet.oc1.iad.aaaa______kfa\"}]" \
   --size 3 \
   --region us-ashburn-1 \
   --node-metadata '{"user_data": "'$(cat my-mgd-ubuntu-cloud-init.yaml | base64 -b 0)'"}'

   The Kubernetes version must match the Kubernetes version you specified in the cloud-init script (see Step 3: Create a cloud-init script to install the Ubuntu node package and bootstrap the worker node).

   Note that the Kubernetes version you specify using the --kubernetes-version parameter must correspond to the Kubernetes version you specified in the cloud-init script (see Step 3: Create a cloud-init script to install the Ubuntu node package and bootstrap the worker node).

Adding Ubuntu worker nodes as self-managed nodes

Before you create a self-managed node, confirm that:

• The cluster to which you want to add the self-managed node is configured appropriately for self-managed nodes. See Cluster Requirements.
• A dynamic group and an IAM policy already exist to allow the compute instance hosting the self-managed node to join an enhanced cluster created with Kubernetes Engine. See Creating a Dynamic Group and a Policy for Self-Managed Nodes.

Using the Console

1. Create a new compute instance to host the self-managed node:
   1. Open the navigation menu  and select Compute. Under Compute, select Instances.
   2. Follow the instructions in the Compute service documentation to create a new compute instance. Note that appropriate policies must exist to allow the new compute instance to join the enhanced cluster. See Creating a Dynamic Group and a Policy for Self-Managed Nodes.
   3. In the Image and Shape section, click Change image.
   4. Click My images, select the Image OCID option, and then enter the OCID of the custom image that you created in Step 1: Create a custom image based on an existing compute instance running the required Ubuntu release.
   5. Click Show advanced options, and on the Management tab, select the Paste cloud-init script option.
   6. Copy and paste the cloud-init script you created for self-managed nodes in Step 3: Create a cloud-init script to install the Ubuntu node package and bootstrap the worker node, into the Cloud-init script field.
   7. Click Create to create the compute instance to host the self-managed node.

   When the compute instance is created, it is added as a self-managed node to the cluster with the Kubernetes API endpoint that you specified in the cloud-init script.

2. (Optional) Verify that the self-managed node has been added to the Kubernetes cluster, and that labels have been added to the node and set as expected, by following the instructions in Creating Self-Managed Nodes.

Using the CLI

1. Open a command prompt and enter the oci Compute instance launch command and required parameters to create a self-managed node.
2. As well as the mandatory parameters required by the command:
   1. Include the --image-id parameter, and specify the OCID of the custom image that you created in Step 1: Create a custom image based on an existing compute instance running the required Ubuntu release.
   2. Include the --user-data-file parameter and specify the cloud-init script that you created for self-managed nodes in Step 3: Create a cloud-init script to install the Ubuntu node package and bootstrap the worker node .

   For example, you might enter the following command:

   oci compute instance launch \
   --availability-domain zkJl:PHX-AD-1 \
   --compartment-id ocid1.compartment.oc1..aaaaaaa______neoq \
   --shape VM.Standard2.2 \
   --subnet-id ocid1.subnet.oc1.phx.aaaaaaa______hzia \
   --user-data-file my-selfmgd-ubuntu-cloud-init.yaml \
   --image-id ocid1.image.oc1.phx.aaaaaaa______slcr

   When the compute instance is created, it is added as a self-managed node to the cluster with the Kubernetes API endpoint that you specified in the cloud-init script.