Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


titleCloud Remote in a Google Cloud region for a Kubernetes cloud

Include Page
Cloud Remote in Google for a Kubernetes Cloud
Cloud Remote in Google for a Kubernetes Cloud

Update Cloud Remote

When updating Workload Manager to Workload Manager 5.0.2 or updating Cost Optimizer to Cost Optimizer 5.0.2, you must also update all instances of Cloud Remote to Cloud Remote 5.0.2. For each instance of Cloud Remote, follow this update procedure.

  1. Locate the Cloud Remote update script at and copy it to a directory in your Cloud Remote instance.
  2. Establish a terminal session to the Cloud Remote instance and navigate to the directory containing the update script.
  3. Run the following commands from the Cloud Remote command prompt.

    chmod +x UPGRADE_FILE
    sudo ./ UPGRADE_FILE

    When the script completes successfully you will get the following message at the command prompt:

    CloudRemote upgraded successfully!

  4. Occasionally, the update script may time out before sending the success message. If you believe this may be the case, you can confirm the update did complete successfully by executing these two commands from the Cloud Remote command prompt:

    1. Confirm all of the images needing update are at the new revision level: 

      Code Block
      docker images

      The output should be similar to the example below.
      Image Added
      The following images should be updated:

      1. ui

      2. ces_worker

      3. worker

      4. guacamole

      5. remoteproxy

      6. rabbitmq

      7. babl

      8. centos_worker

      9. ces_centos_worker

    2. Confirm all of the images have been launched and running in containers:

      Code Block
      docker ps

      The output should be similar to the example below.
      Image Added

  5. After the update script completes successfully, download the region connectivity settings from the Regions tab in the Workload Manager or Cost Optimizer UI as a zip file, then upload that zip file to Cloud Remote as explained in the Cloud Remote configuration instructions above.

  6. After uploading the configuration file to Cloud Remote, manually restart each managed application VM that is in the region served by the updated Cloud Remote instance.


After your initial Cloud Remote instance is launched and configured, it is recommended that you can add two additional nodes to form a cluster. When scaling up or down it is recommended not to run your cluster continuously with only two nodes. Follow this procedure:


Terms & Conditions Privacy Statement Cookies Trademarks