maqpna rollback
Roll the Helm release back to an earlier revision
Synopsis#
maqpna rollback [REVISION] [--wait] [--dry-run] [--force] [--release maqpna] [-n NS] [--timeout 10m]Description#
REVISION defaults to the previous revision ('maqpna status' lists them). The CRDs are not rolled back. Rollback is refused when an installed CRD stores a version the target revision's chart does not define (the old operator could not read those objects); --force overrides.
Flags#
| Flag | Type | Description | Default |
|---|---|---|---|
--debug | switch | print Helm's debug log to stderr | none |
--dry-run | switch | check and print the plan; change nothing | none |
--force | switch | roll back even when CRD stored versions would be unknown to the target revision | none |
--kube-context | string | kubeconfig context (default: the maqpna context's) | none |
-n, --namespace | string | namespace of the MAQPNA control plane (the Helm release) | maqpna-system |
--release | string | Helm release name | maqpna |
--timeout | duration | timeout of Kubernetes operations (CRDs Established, --wait) | 10m0s |
--wait | switch | wait until every workload is ready | none |
The global flags (--context, -o, --no-color, ...) work with every command.
Examples#
maqpna rollback --dry-run
maqpna rollback 3 --waitWhat happens when you run it#
- Runs the lifecycle plugin
maqpna-install(next tomaqpnaor onPATH), which drives the Helm v3 SDK against the cluster of your kubeconfig (--kubeconfig,--kube-context). --dry-run: check and print the plan; change nothing.--force: roll back even when CRD stored versions would be unknown to the target revision.--wait: wait until every workload is ready.- Prints a table by default;
-o jsonor-o yamlprint the data, and--jq EXPRfilters the JSON.
Exit codes#
| Code | Meaning |
|---|---|
0 | success |
1 | error (the message says what failed, with a hint when there is one) |
2 | usage error: unknown flag, missing argument or bad value; the synopsis is printed |
3 | a check failed, a change is blocked, or a result did not match (tamper, policy mismatch) (not used by this command) |
Related commands#
Terminal demo#
This command needs a Kubernetes cluster with MAQPNA installed, so the recording shows its help. Try it against a cluster from Install.