Verrazzano Enterprise Container Platform – Upgrade Verrazzano

Docs: Prepare to Upgrade Verrazzano

Mon, 01 Jan 0001 00:00:00 +0000

A Verrazzano installation consists of a stack of components, such as cert-manager, where each component has a specific release version that may be different from the overall Verrazzano version. The Verrazzano platform operator knows the versions of each component associated with the Verrazzano version. When you perform the initial Verrazzano installation, the appropriate version of each component is installed by the platform operator. Post installation, it may be necessary to update one or more of the component images or Helm charts. This update is also handled by the platform operator and is called an upgrade. Currently, Verrazzano does only patch-level upgrades, where a helm upgrade command can be issued for the component. Typically, patch-level upgrades simply replace component images with newer versions.

Application and system pod restarts

If Verrazzano has a new version of Istio, then all the pods with Istio proxy sidecars need to be restarted. This is done so that the new version of the proxy sidecar can be injected into the pods. All Verrazzano system pods containing Istio proxy sidecars will be restarted. Additionally, OAM application workloads with old versions of the Istio proxy sidecar will be restarted as well. Verrazzano will perform a rolling restart of all OAM workloads, except WebLogic workloads with an Istio proxy sidecar that is out of date by two minor versions or more. For these workloads, Verrazzano will stop the WebLogic domain prior to upgrade and restart it after the upgrade has been completed. This may result in downtime during upgrade for these WebLogic workloads. There is no user involvement related to restarting OAM applications; it is done automatically during upgrade.

Docs: Perform the Verrazzano Upgrade

Mon, 01 Jan 0001 00:00:00 +0000

It is important to distinguish between updating the Verrazzano platform operator versus upgrading the Verrazzano installation. The platform operator contains the newer component charts and image versions, so it must be updated prior to upgrading the installation. Updating the platform operator has no effect on an existing installation until you initiate the Verrazzano installation upgrade. Currently, there is no way to roll back either the platform operator update or the Verrazzano installation upgrade.

You can upgrade Verrazzano using the Verrazzano CLI or with kubectl. See the following respective sections.

NOTE

For optimal functionality, be sure to install or upgrade the CLI version to match the Verrazzano version to which you are upgrading.

Upgrade Verrazzano using the CLI

In one simple step, you can upgrade to a specified version of Verrazzano using this command.

Update the Verrazzano resource to the desired version.

To update to the latest version (default):
```
$ vz upgrade
```
To update to a specific version, where <version> is the desired version:
```
$ vz upgrade --version <version>
```
Wait for the upgrade to complete. Upgrade logs will be streamed to the command window until the upgrade has completed or until the default timeout (30m) has been reached.

Upgrade using kubectl

Upgrading an existing Verrazzano installation is a two-step process:

Update the Verrazzano platform operator to the Verrazzano release version to which you want to upgrade.
Upgrade the Verrazzano installation.

Update the Verrazzano platform operator

In order to upgrade an existing Verrazzano installation, you must first update the Verrazzano platform operator.

Update the Verrazzano platform operator.

NOTE: If you are using a private container registry, then to update the platform operator, follow the instructions at Use a Private Registry.

To update to the latest version:
```
$ kubectl apply -f https://github.com/verrazzano/verrazzano/releases/download/master/verrazzano-platform-operator.yaml
```
To update to a specific version, where <version> is the desired version:
```
# To update to the desired version:
$ kubectl apply -f https://github.com/verrazzano/verrazzano/releases/download/<version>/verrazzano-platform-operator.yaml
```
Wait for the deployment to complete.
```
$ kubectl -n verrazzano-install rollout status deployment/verrazzano-platform-operator
```
```
# Expected response
deployment "verrazzano-platform-operator" successfully rolled out
```
Confirm that the operator pod is correctly defined and running.
```
$ kubectl -n verrazzano-install get pods
```
```
# Sample output
NAME                                            READY   STATUS    RESTARTS   AGE
verrazzano-platform-operator-59d5c585fd-lwhsx   1/1     Running   0          114s
```

Upgrade Verrazzano

To upgrade the Verrazzano installation, you need to change the version of your installed Verrazzano resource to the version supported by the Verrazzano platform operator.

NOTE: You may only change the version field during an upgrade; changes to other fields or component configurations are not supported at this time.

In one simple step, you can upgrade to a specified version of Verrazzano using this command.

$ kubectl patch vz example-verrazzano -p '{"spec":{"version":"master"}}' --type=merge

Alternatively, you can upgrade the Verrazzano installation using the following steps.

Update the Verrazzano resource to the desired version.

To upgrade the Verrazzano components, you must update the version field in your Verrazzano resource spec to match the version supported by the platform operator to which you upgraded and apply it to the cluster.

The value of the version field in the resource spec must be a Semantic Versioning value corresponding to a valid Verrazzano release version.

To update the resource, do one of the following:

a. Edit the YAML file you used to install Verrazzano and set the version field to the latest version.

For example, to upgrade to master, your YAML file should be edited to add or update the version field.
```
apiVersion: install.verrazzano.io/v1beta1
kind: Verrazzano
metadata:
  name: example-verrazzano
spec:
   profile: dev
   version: master
```
Then, apply the resource to the cluster (if you have not edited the resource in-place using kubectl edit).
```
$ kubectl apply -f example-verrazzano.yaml
```
b. Edit the Verrazzano resource directly using kubectl and set the version field directly, for example:
```
$ kubectl edit verrazzano example-verrazzano
# In the resource editor, add or update the version field to "version: master", then save.
```
Wait for the upgrade to complete.
```
$ kubectl wait \
    --timeout=30m \
    --for=condition=UpgradeComplete verrazzano/example-verrazzano
```

Docs: Verify the Upgrade

Mon, 01 Jan 0001 00:00:00 +0000

Check that all the pods in the verrazzano-system namespace are in the Running state. While the upgrade is in progress, you may see some pods terminating and restarting as newer versions of components are applied, for example:

$ kubectl get pods -n verrazzano-system

# Sample output
coherence-operator-866798c99d-r69xt                1/1     Running   1          43m
fluentd-f9fbv                                      2/2     Running   0          38m
fluentd-n79c4                                      2/2     Running   0          38m
fluentd-xslzw                                      2/2     Running   0          38m
oam-kubernetes-runtime-56cdb56c98-wn2mb            1/1     Running   0          43m
verrazzano-application-operator-7c95ddd5b5-7xzmn   1/1     Running   0          42m
verrazzano-authproxy-594d8c8dcd-llmlr              2/2     Running   0          38m
verrazzano-console-74dbf97fdf-zxvvn                2/2     Running   0          38m
verrazzano-monitoring-operator-6fcf8484fd-gfkhs    1/1     Running   0          38m
verrazzano-operator-66c8566f95-8lbs6               1/1     Running   0          38m
vmi-system-es-master-0                             2/2     Running   0          38m
vmi-system-grafana-799d79648d-wsdp4                2/2     Running   0          38m
vmi-system-kiali-574c6dd94d-f49jv                  2/2     Running   0          41m
vmi-system-osd-77f8d998f4-zzvqr   2/2     Running   0          38m
weblogic-operator-7b447fdb47-wlw64                 2/2     Running   0          42m

Check that the pods in your application namespaces are ready, for example:

$ kubectl get pods -n todo-list

# Sample output
NAME                     READY   STATUS    RESTARTS   AGE
mysql-67575d8954-d4vkm   2/2     Running   0          39h
tododomain-adminserver   4/4     Running   0          39h

Docs: Troubleshoot Upgrade Issues

Mon, 01 Jan 0001 00:00:00 +0000

In Verrazzano 1.3 and later, upgrade will continue to run until it succeeds or until you delete the Verrazzano CR. In previous versions, upgrade could fail and transition to the UpgradeFailed state. If that happens, and you updated the Verrazzano platform operator to 1.3+, then the Verrazzano CR will transition to UpgradePaused. To continue with the upgrade, you must change the CR version to the current version of the Verrazzano platform operator. The following steps illustrate this scenario:

You install Verrazzano 1.1.2.
You upgrade to 1.2.0 by changing the Verrazzano CR version field to v1.2.0.
- For some reason, the upgrade failed and the Verrazzano CR state transitions to UpgradeFailed.
You update the Verrazzano platform operator to 1.3.0.
- The Verrazzano CR state transitions to UpgradePaused.
You change the Verrazzano CR version field to v1.3.0.
- The Verrazzano CR state transitions to Upgrading and stays in that state until it completes, then it transitions to UpgradeComplete.

To see detailed progress of the upgrade, view the logs with the following command.

$ kubectl logs -n verrazzano-install \
    -f $(kubectl get pod \
    -n verrazzano-install \
    -l app=verrazzano-platform-operator \
    -o jsonpath="{.items[0].metadata.name}") | grep '^{.*}$' \
    | jq -r '."@timestamp" as $timestamp | "\($timestamp) \(.level) \(.message)"'

For additional troubleshooting help, see Analysis Advice.

Docs: Upgrade Verrazzano in a Multicluster Environment

Mon, 01 Jan 0001 00:00:00 +0000

Each cluster of a multicluster environment is upgraded separately. Start with the admin cluster, and then for each managed cluster, follow the Upgrade Verrazzano instructions.

Verify the upgrade of each managed cluster

For each managed cluster, follow the instructions in each of the following sections: