Table of contents

Upgrading RStudio Server with R 3.6

A project administrator can upgrade the RStudio Server with R 3.6 service on IBM® Cloud Pak for Data.

Before you begin

Required role: To complete this task, you must be an administrator of the project (namespace) where RStudio Server with R 3.6 is installed.

Before you upgrade RStudio Server with R 3.6, ensure that:

Common core services RStudio Server with R 3.6 requires the Cloud Pak for Data common core services. The common core services are installed once in a given Red Hat OpenShift project. If the common core services are not installed in the project where you plan to install RStudio Server with R 3.6 or if the common core services are not at the correct version, the common core services will be automatically installed or upgraded when you upgrade RStudio Server with R 3.6. If the common core services need to be installed or upgraded, it might take longer to upgrade RStudio Server with R 3.6. For more information on the common core services, see:

If you are upgrading multiple services on your cluster, you must run the upgrades one at a time and wait until the upgrade completes before upgrading another service. You cannot run the upgrades in parallel.

Tip: For a list of all available options, enter the following command:
./cpd-cli upgrade --help

Procedure

  1. Complete the appropriate steps to upgrade RStudio Server with R 3.6 on your environment:
  2. Verifying that the upgrade completed successfully
  3. Checking for available patches
  4. Complete the tasks listed in What to do next

Upgrading on clusters connected to the internet

From your installation node:

  1. Change to the directory where you placed the Cloud Pak for Data command-line interface and the repo.yaml file.
  2. Log in to your Red Hat OpenShift cluster as a project administrator:
    oc login OpenShift_URL:port
  3. Run the following command to see a preview of what will change when you upgrade the service.
    Important: If you are using the internal Red Hat OpenShift registry and you are using the default self-signed certificate, specify the --insecure-skip-tls-verify flag to prevent x509 errors.
    ./cpd-cli upgrade \
--repo ./repo.yaml \
--assembly rstudio \
--arch Cluster_architecture \  
--namespace Project \
--storageclass Storage_class_name \
--transfer-image-to Registry_location \
--cluster-pull-prefix Registry_from_cluster \
--ask-pull-registry-credentials \
--ask-push-registry-credentials \
--latest-dependency \
--dry-run
    If you are upgrading with Portworx storage, add the following line to your upgrade command after the --storageclass flag:
    --override-config portworx \
    If you are upgrading with OpenShift Container Storage, add the following line to your upgrade command after the --storageclass flag:
    --override-config ocs \

    Replace the following values:

    Variable Replace with
    Cluster_architecture Specify the architecture of your cluster hardware:
    • For x86-64 hardware, remove this flag or specify x86_64
    Project Use the value provided by your cluster administrator. You should have obtained this information when you completed Preparing to install and upgrade services.
    Storage_class_name Use the value provided by your cluster administrator. You should have obtained this information when you completed Preparing to install and upgrade services.
    Registry_location Use the value provided by your cluster administrator. You should have obtained this information when you completed Preparing to install and upgrade services.
    Registry_from_cluster Use the value provided by your cluster administrator. You should have obtained this information when you completed Preparing to install and upgrade services.
  4. Rerun the previous command without the --dry-run flag to upgrade the service.

Upgrading on air-gapped clusters

From your installation node:

  1. Change to the directory where you placed the Cloud Pak for Data command-line interface.
  2. Log in to your Red Hat OpenShift cluster as a project administrator:
    oc login OpenShift_URL:port
  3. Run the following command to see a preview of what will change when you upgrade the service.
    Important: If you are using the internal Red Hat OpenShift registry:
    • Do not specify the --ask-pull-registry-credentials parameter.
    • If you are using the default self-signed certificate, specify the --insecure-skip-tls-verify flag to prevent x509 errors.
    ./cpd-cli upgrade \
--assembly rstudio \
--arch Cluster_architecture \
--namespace Project \
--storageclass Storage_class_name \
--cluster-pull-prefix Registry_from_cluster \
--ask-pull-registry-credentials \
--load-from Image_directory_location \
--latest-dependency \
--dry-run
    If you are upgrading with Portworx storage, add the following line to your upgrade command after the --storageclass flag:
    --override-config portworx \
    If you are upgrading with OpenShift Container Storage, add the following line to your upgrade command after the --storageclass flag:
    --override-config ocs \

    Replace the following values:

    Variable Replace with
    Cluster_architecture Specify the architecture of your cluster hardware:
    • For x86-64 hardware, remove this flag or specify x86_64
    Project Use the value provided by your cluster administrator. You should have obtained this information when you completed Preparing to install and upgrade services.
    Storage_class_name Use the value provided by your cluster administrator. You should have obtained this information when you completed Preparing to install and upgrade services.
    Registry_location Use the value provided by your cluster administrator. You should have obtained this information when you completed Preparing to install and upgrade services.
    Registry_from_cluster Use the value provided by your cluster administrator. You should have obtained this information when you completed Preparing to install and upgrade services.
  4. Rerun the previous command without the --dry-run flag to upgrade the service.

Verifying that the upgrade completed successfully

From your installation node:

  1. Run the following command:
    ./cpd-cli status \
--assembly rstudio \
--namespace Project

    Replace Project with the value you used in the preceding commands.

Checking for available patches

Determine whether there are any patches available the version of RStudio Server with R 3.6 that you installed:

Clusters connected to the internet
Run the following command to check for patches:
./cpd-cli status \
--repo ./repo.yaml \
--namespace Project \ 
--assembly rstudio \
--patches \
--available-updates
Air-gapped clusters
See the list of Available patches for RStudio Server with R 3.6.

If you need to apply patches to the service, follow the guidance in Applying patches.

What to do next

The service is ready to use. For details, see Analyzing data with RStudio