Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Update the OS

You create the node virtual machines (VMs) in a Routing Director deployment cluster using the OVA (or OVF and .vmdk) software download files. The files are pre-packaged with all the utilities, OS, and software required to create the VMs. The VMs are created with Ubuntu 22.04.5 LTS (Jammy Jellyfish) Linux base OS. You might need to update the base OS to maintain the security, stability, performance, and compatibility of the Kubernetes cluster. Juniper provides you with the required OS update file to enable you to update the OS on your node VMs. The OS update functionality in Routing Director includes the following updates:

  • Linux kernel update

  • OpenSSL or OS security update

  • Any third-party packages required by Routing Director

  • All packages that are part of the base OS

To update the OS, perform the following steps:

  1. Download the routing-director-ubuntu-22-04-update-date.tar.gz and routing-director-ubuntu-22-04-update-date.tar.gz.psig files from the Juniper Software Download site on to your computer or local installer VM.
  2. Log in to any one of the Routing Director deployment cluster nodes as the root user.
  3. Type exit to exit Deployment Shell to the Linux root shell.
  4. Copy the routing-director-ubuntu-22-04-update-date.tar.gz and routing-director-ubuntu-22-04-update-date.tar.gz.psig files to the cluster node.
  5. Update the OS on the current node using the copied files.

    The process takes around 15-30 minutes to complete depending on the size of the updated packages. Once complete, the OS versions on the other three nodes of the cluster are also automatically updated.

  6. (Optional) In some cases, when the kernel is upgraded, you might see a message similar to the following on-screen:
    Perform the following steps to reboot the cluster:

    1. Log in to Deployment Shell.

    2. Reboot the cluster nodes.

      All the cluster nodes are rebooted at the same time. After the nodes are rebooted, we recommend that you wait for a few minutes to ensure that the cluster is back online.

  7. Verify that the cluster is healthy and operational from the Deployment Shell.

Verify the OS update

Perform any of the following steps to verify that the OS update process is successful, and the cluster operation is unaffected.

  • The Routing Director deployment cluster remains operational while updating the OS. To verify if the update process has succeeded, check the /var/log/apt/history.log log file to see the timestamp of the last update and updated packages. For example:

  • Verify that cluster-operation is unaffected by checking that all pods are in Running status using the following command in Deployment Shell.