Single cluster

Uninstall Gloo Mesh Gateway from a single-cluster setup.

Gateway proxies

Uninstall the Istio control plane and gateway proxies. Note: For demo installations, skip to the next section.

  1. Delete the GatewayLifecycleManager resource for the gateway proxy.

      kubectl delete GatewayLifecycleManager istio-ingressgateway -n gloo-mesh

  2. Verify that the gateway resources are removed before you proceed to the next step.

      kubectl get all -n gloo-mesh-gateways

  3. Delete the IstioLifecycleManager for the istiod control plane. Note that your resource might have a different name.

      kubectl delete IstioLifecycleManager gloo-platform -n gloo-mesh

  4. Verify that the Istio resources are removed before you proceed to the next step.

      # Change the revision as needed
kubectl get all -n gm-iop-1-22
kubectl get all -n istio-system

  5. Delete the Istio namespaces.

      kubectl delete ns istio-system
kubectl delete ns gloo-mesh-gateways

  1. Find the name of your Istio Helm chart release in the gloo-mesh-gateways namespace, such as istio-ingressgateway-1-22.

      helm ls -n gloo-mesh-gateways

  2. Delete the Helm release for the ingress gateway.

      helm delete istio-ingressgateway-1-22 -n gloo-mesh-gateways

  3. Find the name of your Istio Helm chart release in the istio-system namespace, such as istiod-1-22.

      helm ls -n istio-system

  4. Delete the Helm release for the istiod control plane.

      helm delete istiod-1-22 -n istio-system

  5. Delete the Istio namespaces.

      kubectl delete ns istio-system
kubectl delete ns gloo-mesh-gateways
kubectl delete ns istio-config

OpenShift installations: Revoke the extra permissions and resources required for OpenShift to run Istio.

  1. Revoke the Istio namespace ID permissions for the Istio service accounts.

      oc adm policy remove-scc-from-group anyuid system:serviceaccounts:gloo-mesh
oc adm policy remove-scc-from-group anyuid system:serviceaccounts:istio-system
oc adm policy remove-scc-from-group anyuid system:serviceaccounts:gloo-mesh-gateways
# Update revision as needed
oc adm policy remove-scc-from-group anyuid system:serviceaccounts:gm-iop-1-22

  2. Revoke the Istio namespace ID permissions for sample app project service accounts.

      oc adm policy remove-scc-from-group anyuid system:serviceaccounts:bookinfo
oc adm policy remove-scc-from-group anyuid system:serviceaccounts:httpbin

  3. Delete the NetworkAttachmentDefinition resources and the Istio namespace ID permissions for your workload projects.

      oc adm policy remove-scc-from-group anyuid system:serviceaccounts:<workload_projects>
  
      oc delete network-attachment-definition istio-cni -n <workload_projects>

Gloo Mesh Gateway

  1. Uninstall Gloo Mesh Gateway.

      meshctl uninstall --purge

    Note: If you see a warning such as release gloo-platform does not exist, nothing to uninstall, use the Helm tab instead.

    1. Uninstall the main Gloo Mesh Gateway release.
        meshctl uninstall
    2. Uninstall the Gloo CRDs Helm release.
        helm uninstall gloo-platform-crds -n gloo-mesh

    Note: If you see a warning such as release gloo-platform does not exist, nothing to uninstall, use the Helm tab instead.

    1. Delete the KubernetesCluster resource from the cluster.
        kubectl delete kubernetescluster $CLUSTER_NAME -n gloo-mesh
    2. Uninstall the main Gloo Mesh Gateway release. Note that your Helm release might have a different name.
        helm uninstall gloo-platform -n gloo-mesh
    3. If you maintained a separate gloo-agent-addons Helm release, uninstall the release. Note that your add-ons might be installed in a different namespace, such as gloo-mesh-addons.
        helm uninstall gloo-agent-addons -n gloo-mesh
    4. Uninstall the Gloo CRDs Helm release.
        helm uninstall gloo-platform-crds -n gloo-mesh

  2. Delete the gloo-mesh namespace.

      kubectl delete namespace gloo-mesh

Optional: Sample apps

If you installed the Bookinfo and httpbin sample apps, run the following commands to uninstall their resources.

  1. Export the Istio version that your cluster runs as an environment variable, such as 1.22.4 in the following example.

      export ISTIO_VERSION=1.22.4

  2. Remove the Bookinfo application components and service accounts.

      kubectl -n bookinfo delete -f https://raw.githubusercontent.com/istio/istio/$ISTIO_VERSION/samples/bookinfo/platform/kube/bookinfo.yaml -l 'app,version notin (v3)'
kubectl -n bookinfo delete -f https://raw.githubusercontent.com/istio/istio/$ISTIO_VERSION/samples/bookinfo/platform/kube/bookinfo.yaml -l 'account'

  3. Delete the bookinfo namespace.

      kubectl delete ns bookinfo

  4. Remove the httpbin application components.

      kubectl -n httpbin delete -f https://raw.githubusercontent.com/solo-io/gloo-mesh-use-cases/main/policy-demo/httpbin.yaml

  5. Delete the httpbin namespace.

      kubectl delete ns httpbin

Multicluster

Uninstall Gloo Mesh Gateway from a multicluster setup.

Gateway proxies

  1. Save the names and contexts of the clusters you want to uninstall Gloo Mesh Gateway from.

      export MGMT_CLUSTER=<management-cluster>
export REMOTE_CLUSTER1=<remote-cluster1>
export REMOTE_CLUSTER2=<remote-cluster2>
  
      export MGMT_CONTEXT=<management-cluster-context>
export REMOTE_CONTEXT1=<remote-cluster1-context>
export REMOTE_CONTEXT2=<remote-cluster2-context>

  2. Uninstall the Istio control plane and gateway proxies. These steps differ depending on how you installed them.

    1. Delete the GatewayLifecycleManager resources for the gateway proxies.
        kubectl delete GatewayLifecycleManager  -n gloo-mesh --context $MGMT_CONTEXT
kubectl delete GatewayLifecycleManager istio-eastwestgateway -n gloo-mesh --context $MGMT_CONTEXT
    2. Verify that the gateway resources are removed before you proceed to the next step.
        kubectl get all -n gloo-mesh-gateways --context $REMOTE_CONTEXT1
kubectl get all -n gloo-mesh-gateways --context $REMOTE_CONTEXT2
    3. Delete the IstioLifecycleManager for the istiod control plane. Note that your resource might have a different name.
        kubectl delete IstioLifecycleManager gloo-platform -n gloo-mesh --context $MGMT_CONTEXT
    4. Verify that the Istio resources are removed before you proceed to the next step.
        # Change the revision as needed
kubectl get all -n gm-iop-1-22 --context $REMOTE_CONTEXT1
kubectl get all -n istio-system --context $REMOTE_CONTEXT1
    5. Delete the Istio namespaces from the workload clusters.
        kubectl delete ns istio-sustem --context $REMOTE_CONTEXT1
kubectl delete ns gloo-mesh-gateways --context $REMOTE_CONTEXT1
  
        kubectl delete ns istio-system --context $REMOTE_CONTEXT2
kubectl delete ns gloo-mesh-gateways --context $REMOTE_CONTEXT2

    1. Find the name of your Istio Helm chart releases in the gloo-mesh-gateways namespace, such as istio-ingressgateway-1-22 and istio-eastwestgateway-1-22.

        helm ls -n gloo-mesh-gateways

    2. Delete the Helm release for the ingress and east-west gateways.

        helm delete istio-ingressgateway-1-22 -n gloo-mesh-gateways
helm delete istio-eastwestgateway-1-22 -n gloo-mesh-gateways

    3. Find the name of your Istio Helm chart release in the istio-system namespace, such as istiod-1-22.

        helm ls -n istio-system

    4. Delete the Helm release for the istiod control plane.

        helm delete istiod-1-22 -n istio-system

    5. Delete the Istio namespaces.

        kubectl delete ns istio-system --context $REMOTE_CONTEXT1
kubectl delete ns gloo-mesh-gateways --context  $REMOTE_CONTEXT1
kubectl delete ns istio-config --context $REMOTE_CONTEXT1
  
        kubectl delete ns istio-system --context $REMOTE_CONTEXT2
kubectl delete ns gloo-mesh-gateways --context $REMOTE_CONTEXT2
kubectl delete ns istio-config --context $REMOTE_CONTEXT2

  3. OpenShift installations: Revoke the extra permissions and resources required for OpenShift to run Istio.

    1. Revoke the Istio namespace ID permissions for the Istio service accounts.

        oc adm policy remove-scc-from-group anyuid system:serviceaccounts:gloo-mesh --context $REMOTE_CONTEXT1
oc adm policy remove-scc-from-group anyuid system:serviceaccounts:istio-system --context $REMOTE_CONTEXT1
oc adm policy remove-scc-from-group anyuid system:serviceaccounts:gloo-mesh-gateways --context $REMOTE_CONTEXT1
# Update revision as needed
oc adm policy remove-scc-from-group anyuid system:serviceaccounts:gm-iop- --context $REMOTE_CONTEXT1
  
        oc adm policy remove-scc-from-group anyuid system:serviceaccounts:gloo-mesh --context $REMOTE_CONTEXT2
oc adm policy remove-scc-from-group anyuid system:serviceaccounts:istio-system --context $REMOTE_CONTEXT2
oc adm policy remove-scc-from-group anyuid system:serviceaccounts:gloo-mesh-gateways --context $REMOTE_CONTEXT2
# Update revision as needed
oc adm policy remove-scc-from-group anyuid system:serviceaccounts:gm-iop- --context $REMOTE_CONTEXT2

    2. Revoke the Istio namespace ID permissions for sample app project service accounts.

        oc --context $REMOTE_CONTEXT1 adm policy remove-scc-from-group anyuid system:serviceaccounts:bookinfo
oc --context $REMOTE_CONTEXT1 adm policy remove-scc-from-group anyuid system:serviceaccounts:httpbin
  
        oc --context $REMOTE_CONTEXT2 adm policy remove-scc-from-group anyuid system:serviceaccounts:bookinfo
oc --context $REMOTE_CONTEXT2 adm policy remove-scc-from-group anyuid system:serviceaccounts:httpbin

    3. Delete the NetworkAttachmentDefinition resources and the Istio namespace ID permissions for your workload projects.

        oc --context $REMOTE_CONTEXT1 adm policy remove-scc-from-group anyuid system:serviceaccounts:<workload_projects>
oc --context $REMOTE_CONTEXT2 adm policy remove-scc-from-group anyuid system:serviceaccounts:<workload_projects>
  
        oc --context $REMOTE_CONTEXT1 delete network-attachment-definition istio-cni -n <workload_projects>
oc --context $REMOTE_CONTEXT2 delete network-attachment-definition istio-cni -n <workload_projects>

Workload clusters

Uninstall the Gloo data plane components from the workload clusters.

  1. Uninstall the Gloo agent that runs on each workload cluster.

    1. Deregister cluster1.
        meshctl cluster deregister \
  --kubecontext $MGMT_CONTEXT \
  --remote-context $REMOTE_CONTEXT1 \
  $REMOTE_CLUSTER1
      Example output:
        Deregistering cluster: cluster1
Finished uninstalling release gloo-mesh-agent
Successfully deregistered cluster: cluster1
    2. Deregister cluster2.
        meshctl cluster deregister \
  --kubecontext $MGMT_CONTEXT \
  --remote-context $REMOTE_CONTEXT2 \
  $REMOTE_CLUSTER2
    1. If you maintained a separate gloo-agent-addons Helm release, uninstall the release. Note that your add-ons might be installed in a different namespace, such as gloo-mesh-addons.
        helm uninstall gloo-agent-addons -n gloo-mesh --kube-context $REMOTE_CONTEXT1
helm uninstall gloo-agent-addons -n gloo-mesh --kube-context $REMOTE_CONTEXT2
    2. Uninstall the agent Helm releases. Note that your Helm release might have a different name.
        helm uninstall gloo-platform -n gloo-mesh --kube-context $REMOTE_CONTEXT1
helm uninstall gloo-platform -n gloo-mesh --kube-context $REMOTE_CONTEXT2
    3. Delete the corresponding KubernetesCluster resources from the management cluster.
        kubectl delete kubernetescluster $REMOTE_CLUSTER1 $REMOTE_CLUSTER2 -n gloo-mesh --context $MGMT_CONTEXT
    4. Delete the relay secrets from each workload cluster, as you cannot reuse the same secret if you decide to re-register the agent later.
        kubectl delete secret -n gloo-mesh relay-client-tls-secret --context $REMOTE_CONTEXT1
kubectl delete secret -n gloo-mesh relay-identity-token-secret --context $REMOTE_CONTEXT1
kubectl delete secret -n gloo-mesh relay-root-tls-secret --context $REMOTE_CONTEXT1
  
        kubectl delete secret -n gloo-mesh relay-client-tls-secret --context $REMOTE_CONTEXT2
kubectl delete secret -n gloo-mesh relay-identity-token-secret --context $REMOTE_CONTEXT2
kubectl delete secret -n gloo-mesh relay-root-tls-secret --context $REMOTE_CONTEXT2

  2. Uninstall the Gloo CRDs Helm releases in each workload cluster.

      helm uninstall gloo-platform-crds -n gloo-mesh --kube-context $REMOTE_CONTEXT1
helm uninstall gloo-platform-crds -n gloo-mesh --kube-context $REMOTE_CONTEXT2

  3. Delete the gloo-mesh namespace from each workload cluster.

      kubectl --context $REMOTE_CONTEXT1 delete namespace gloo-mesh
kubectl --context $REMOTE_CONTEXT2 delete namespace gloo-mesh

  4. Repeat these steps for any other cluster that is registered with Gloo Mesh. For example, if you ran the management plane in a cluster that was also registered, repeat these steps for the MGMT_CLUSTER and specify the MGMT_CONTEXT. If you registered multiple workload clusters, repeat these steps for each workload cluster.

Management cluster

Uninstall the Gloo management plane components from the management cluster.

  1. Uninstall the Gloo management plane components.

      meshctl uninstall --purge --kubecontext $MGMT_CONTEXT

    Note: If you see a warning such as release gloo-platform does not exist, nothing to uninstall, use the Helm tab instead.

      meshctl uninstall --kubecontext $MGMT_CONTEXT

    Note: If you see a warning such as release gloo-platform does not exist, nothing to uninstall, use the Helm tab instead.

    Note that your Helm release might have a different name.

      helm uninstall gloo-platform -n gloo-mesh --kube-context $MGMT_CONTEXT

  2. Uninstall the Gloo CRDs Helm release from the management cluster.

      helm uninstall gloo-platform-crds -n gloo-mesh --kube-context $MGMT_CONTEXT

  3. Delete the gloo-mesh namespace, and if applicable, the gloo-mesh-config namespace.

      kubectl --context $MGMT_CONTEXT delete namespace gloo-mesh
kubectl --context $MGMT_CONTEXT delete namespace gloo-mesh-config

Optional: Sample apps

If you installed the Bookinfo and httpbin sample apps, run the following commands to uninstall their resources.

  1. Export the Istio version that your cluster runs as an environment variable, such as 1.22.4 in the following example.

      export ISTIO_VERSION=1.22.4

  2. Remove the Bookinfo application components and service accounts.

      kubectl -n bookinfo delete -f https://raw.githubusercontent.com/istio/istio/$ISTIO_VERSION/samples/bookinfo/platform/kube/bookinfo.yaml -l 'app,version notin (v3)' --context $REMOTE_CONTEXT1
kubectl -n bookinfo delete -f https://raw.githubusercontent.com/istio/istio/$ISTIO_VERSION/samples/bookinfo/platform/kube/bookinfo.yaml -l 'app,version notin (v3)' --context $REMOTE_CONTEXT2
kubectl -n bookinfo delete -f https://raw.githubusercontent.com/istio/istio/$ISTIO_VERSION/samples/bookinfo/platform/kube/bookinfo.yaml -l 'account' --context $REMOTE_CONTEXT1
kubectl -n bookinfo delete -f https://raw.githubusercontent.com/istio/istio/$ISTIO_VERSION/samples/bookinfo/platform/kube/bookinfo.yaml -l 'account' --context $REMOTE_CONTEXT2

  3. Delete the bookinfo namespace.

      kubectl delete ns bookinfo --context $REMOTE_CONTEXT1
kubectl delete ns bookinfo --context $REMOTE_CONTEXT2

  4. Remove the httpbin application components.

      kubectl -n httpbin delete -f https://raw.githubusercontent.com/solo-io/gloo-mesh-use-cases/main/policy-demo/httpbin.yaml --context $REMOTE_CONTEXT1
kubectl -n httpbin delete -f https://raw.githubusercontent.com/solo-io/gloo-mesh-use-cases/main/policy-demo/httpbin.yaml --context $REMOTE_CONTEXT2

  5. Delete the httpbin namespace.

      kubectl delete ns httpbin --context $REMOTE_CONTEXT1
kubectl delete ns httpbin --context $REMOTE_CONTEXT2