Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Upgrading the Host OS on the Cluster Server



  • Ensure all Kubernetes pods are running normally. Issue the kubectl get pods command from the control machine or the master node and verify that all Kubernetes pods are READY and have a STATUS of Running.

  • The server that you are upgrading has access to the Internet to download the new host OS release.

  • You have the common secret that you specified when you ran the proNX Optical Director installation script for the current installation.


    If you have forgotten the common secret, you can retrieve it by issuing the following commands from the master node:

    • Type kubectl get secret common.secret -o yaml to retrieve the encoded password.

    • Type echo '<encoded-password>' | base64 --decode to see the encoded password in clear text.

Use this procedure to upgrade the host operating system on each server in the cluster. Once you start, you must upgrade the host operating system on all three servers. The typical procedure is to upgrade the regular nodes first and the master node last.


Although this procedure does not cause any application downtime, it is recommended that you not use the proNX Optical Director to make any configuration changes while this upgrade is taking place.

This procedure shows an upgrade from Atomic Host 7.1805 to 7.1808 as an example. The same steps apply to upgrading from and to other releases.

  1. Log in to one of the servers. For example:
  2. Show the Atomic Host version you are currently running. For example:
  3. Upgrade the host OS. For example:
  4. Reboot the server.
  5. After the server has rebooted, log back in to the server to verify that the server is running the new version of the OS. For example:
  6. From the control machine, verify that the Kubernetes pods are READY and have a STATUS of Running and the databases have been rebalanced. You should perform this step from the control machine because the kubectl utility has not yet been reinstalled on the node with the upgraded host operating system.
    • Check the application database pods. For example:

    • Check to make sure each database has been rebalanced. Rebalancing can take an hour or longer. If the rebalance is complete, you will see a status of notRunning. For example:

      where <common-secret> is the common secret you specified when you installed the current version of the proNX Optical Director software.

    Do not proceed until you have confirmed that the Kubernetes pods are READY and have a STATUS of Running and the databases have been rebalanced.

  7. Repeat this procedure on the next server until all the servers are upgraded.