Roll Back a Calico Networking Change¶

The Tigera Operator reconciles the running state to match the Installation CR, so you roll back a change by setting the changed field back to its original value.

Note

Record the original value before making a change so you can restore it if needed.

Procedure

Patch the field back to its previous value. For example, to revert a logging change:

~(keystone_admin)]$ kubectl patch installation default --type=merge -p '
spec:
  logging:
    cni:
      logSeverity: Warning
'

Monitor reconciliation until the operator reports the reverted state.
```
~(keystone_admin)]$ kubectl get tigerastatus -w
```

Important

Do not roll back by re-applying a full CR captured with kubectl get installation default -o yaml. Such a file contains a stale resourceVersion and kubectl apply is rejected with a conflict error. Use kubectl patch or kubectl edit to change the specific field instead.

For the full set of verification checks, see Monitor Calico Network Operator Status.

Roll Back a Calico Networking Change

Roll Back a Calico Networking Change¶

StarlingX