Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Current »

In the case of a failed upgrade, the system can be downgraded manually using the commands below.

Persistent Storage is required for a possible downgrade

Downgrade will only work in the case of Persistent Storage is defined and is in use, prior to the downgrade.

For information about Persistent Storage, see Persistent Storage[hide]2.2[/hide] (2.2).

Note:

Collect log and error data prior to the downgrade, to be able to analyze the problems.

List available PODs:
$ kubectl get pod --namespace <namespace>

Repeat the command for all PODs:
$ kubectl describe pod <pod> --namespace <namespace>

Repeat the command for all PODs:
kubectl logs <pod> --namespace <namespace>

  1. Downgrade the system with the following commands:

    Identify the correct revision for the rollback:
$ helm list --namespace <namespace>

$ helm rollback  <RELEASE> [REVISION] --namespace <namespace>

  2. Verify that the downgrade was successful with the following command:

    Verify that the pods are up and running:
$ kubectl get pods --namespace <namespace>
  • No labels