Step 5. Remove the Axway Mesh and Agents from your Cluster

Step 5. Remove the Axway Mesh and Agents from your Cluster

Remove the Istio deployment

You can remove the istio and Amplify Central hybrid deployments, but note that these steps remove the namespaces (to be thorough), so you need to go back and regenerate the SMA and CSA secrets (following those procedures) to re-create the various namespaces and regenerate their secrets correctly before you can re-deploy. Use the following commands:

istioctl manifest generate --set profile=demo -f istio-override.yaml| kubectl delete -f -

kubectl get clusterroles.rbac.authorization.k8s.io | grep istio | cut -d " " -f 1 | grep -v NAME | xargs kubectl delete clusterroles.rbac.authorization.k8s.io 

kubectl delete namespace istio-system

Note: If you are deleting Istio from a mesh deployed with an older version Istio i.e Istio 1.5 or below, please refer to the commands below

helm uninstall istio-init 

helm uninstall istio 

kubectl delete validatingwebhookconfiguration istio-galley

kubectl --kube-context "${CONTEXT}" get clusterroles.rbac.authorization.k8s.io | grep istio | cut -d " " -f 1 | grep -v NAME | xargs kubectl delete clusterroles.rbac.authorization.k8s.io

kubectl delete namespace istio-system #If existing

Remove the Amplify Central deployment

There are several steps required to fully remove an Amplify Central Hybrid deployment from a k8s cluster. There are several namespaces that must also be specifically removed after the helm chart has removed other artifacts from the environment. Use the following commands:

helm uninstall apic-hybrid

kubectl delete namespace apic-control

kubectl delete namespace apic-demo