Stopping the v2018 to v10 management upgrade

You can stop the v2018 to v10 upgrade process.

About this task

If you do not want to continue a management upgrade in case of a failure, you can remove the upgrade artifacts.

Procedure

Ensure that either the management upgrade operator is in either Failed state, or the upgrade process has not yet created management.upgradefromv2018.apiconnect.ibm.com.
If you started the upgrade process and are ready to abandon it, clean up the artifacts from the management upgrade. See Cleaning up a failed management upgrade.
Delete the all the upgrade CRDs and management upgrade resources. From the location of the downloaded files, run:
1. Delete all the left over upgrade resources:
  - If upgrading a v2018 single namespace:
```
kubectl delete -f ibm-apiconnect-upgrade-crds.yaml
```
  - If upgrading a v2018 multi-namespace:
```
kubectl delete -f ibm-apiconnect-upgrade-distributed.yaml -n <management-subsystem-namespace>
```
2. Delete all the left over v10 resources:
  - If upgrading a v2018 single namespace:
```
kubectl delete -f ibm-apiconnect.yaml -n <v10-operator-namespace>
```
  - If upgrading a v2018 multi-namespace:
```
kubectl delete -f ibm-apiconnect-distributed.yaml -n <v10-operator-namespace>
```

Delete DataPower resources:

kubectl delete -f ibm-datapower.yaml -n <gateway-namespace>

Delete cert manager and ingress-issuer resources applied in each namespace:

kubectl delete -f <path-to-cert-manager>/cert-manager-0.10.1.yaml
kubectl delete -f <path-to-ingress-issure>/ingress-issuer-v1-alpha1.yaml -n <namespace>