Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.
Chapter 6. Upgrading CodeReady Workspaces
CodeReady Workspaces 1.1.0 introduces an operator that uses a controller to watch custom resources. There is no direct upgrade path from CodeReady Workspaces 1.0.1 to CodeReady Workspaces 1.1.0. If you do not have any important workspaces and projects in an existing 1.0.1 namespace, we recommend deleting the 1.0.1 installation and deploying CodeReady Workspaces 1.1.0.
To keep data from an existing 1.0.1 installation, it is possible to upgrade by deploying the new operator to an existing namespace. You can use the manual or the script-based method to upgrade.
6.1. Upgrading CodeReady Workspaces manually Link kopierenLink in die Zwischenablage kopiert!
Prerequisites
- A running instance of Red Hat OpenShift Container Platform 3.11 or OpenShift Dedicated 3.11.
-
The user is logged in to the OpenShift instance (using, for example,
oc login).
Procedure
Obtain the current PostgreSQL password (
POSTGRESQL_PASSWORD) from the existing PostgreSQL deployment environment, or run the followingoccommand:oc get deployment postgres --output=jsonpath= \ {'.spec.template.spec.containers[0].env \ [?(@.name=="POSTGRESQL_PASSWORD")].value'} --namespace=<codeready>$ oc get deployment postgres --output=jsonpath= \ {'.spec.template.spec.containers[0].env \ [?(@.name=="POSTGRESQL_PASSWORD")].value'} --namespace=<codeready>Copy to Clipboard Copied! Toggle word wrap Toggle overflow ImportantSubstitute
<codeready>for the namespace that you are using.Obtain the current Red Hat SSO administrator username and password (
SSO_ADMIN_USERNAMEandSSO_ADMIN_PASSWORD) from the existing Red Hat SSO deployment environment, or run the followingoccommands:Copy to Clipboard Copied! Toggle word wrap Toggle overflow Note- If you have changed the Red Hat SSO administrator password, provide the new password instead of fetching it from the environment variables.
-
Substitute
<codeready>for the namespace that you are using.
Replace the following values in the
custom-resource.yamlfile with the values you have obtained:Copy to Clipboard Copied! Toggle word wrap Toggle overflow If you have configured OpenShift oAuth, obtain the oAuth secret and set its value in the
custom-resource.yamlfile:To obtain the secret, run the following command as the cluster administrator:
oc get oauthclient openshift-identity-provider-h2fh \ -o=jsonpath= {'.secret'}$ oc get oauthclient openshift-identity-provider-h2fh \ -o=jsonpath= {'.secret'}Copy to Clipboard Copied! Toggle word wrap Toggle overflow Add the following fields to the
spec.authsection of thecustom-resource.yamlfile. SetoAuthClientNametoopenshift-identity-provider-h2fhif not already set.spec: auth: oAuthClientName: 'openshift-identity-provider-h2fh' oAuthSecret: '<secret>'spec: auth: oAuthClientName: 'openshift-identity-provider-h2fh' oAuthSecret: '<secret>'Copy to Clipboard Copied! Toggle word wrap Toggle overflow ImportantSubstitute
<secret>for an actual secret.
To deploy the operator to an existing namespace, run the deployment script with the arguments that suit your installation. See Section 2.2, “Running the CodeReady Workspaces deployment script” for detailed instructions.
./deploy.sh --deploy
$ ./deploy.sh --deployCopy to Clipboard Copied! Toggle word wrap Toggle overflow
6.2. Upgrading CodeReady Workspaces using a migration script Link kopierenLink in die Zwischenablage kopiert!
The upgrade process using the migrate.sh script is an automation of the manual steps listed in the preceding manual section.
Prerequisites
- A running instance of Red Hat OpenShift Container Platform 3.11 or OpenShift Dedicated 3.11.
-
The user is logged in to the OpenShift instance (using, for example,
oc login).
Procedure
Run the
migrate.shscript with the name of your existing deployed project:./migrate.sh --project=codeready
$ ./migrate.sh --project=codereadyCopy to Clipboard Copied! Toggle word wrap Toggle overflow In the above command, substitute
codereadyfor the name of the OpenShift project that you used for deploying the previous version of CodeReady Workspaces.-
Check changes in the
custom-resource.yamlfile. -
Run the
deploy.shscript with parameters for your environment. See Section 2.2, “Running the CodeReady Workspaces deployment script” for detailed instructions.