Remove Istio objects after upgrading MKE

With NGINX Ingress Controller replacing Istio Ingress in MKE 3.5, following an upgrade to any MKE 3.5 iteration it is necessary to remove various Istio Ingress artifacts from your cluster:

• Any remaining Istio Custom Resource Definitions (CRDs)

• The istio-system namespace

Do not remove these artifacts, however, if you plan to continue using a custom Istio installation in your MKE 3.5.x clusters.

To remove Istio objects:

1. Download and configure the client bundle.

2. Delete the Istio CRDs:

   kubectl delete crds \
    adapters.config.istio.io \
    attributemanifests.config.istio.io \
    clusterrbacconfigs.rbac.istio.io \
    destinationrules.networking.istio.io \
    envoyfilters.networking.istio.io \
    gateways.networking.istio.io \
    handlers.config.istio.io \
    httpapispecbindings.config.istio.io \
    httpapispecs.config.istio.io \
    instances.config.istio.io \
    meshpolicies.authentication.istio.io \
    policies.authentication.istio.io \
    quotaspecbindings.config.istio.io \
    quotaspecs.config.istio.io \
    rbacconfigs.rbac.istio.io \
    rules.config.istio.io \
    serviceentries.networking.istio.io \
    servicerolebindings.rbac.istio.io \
    serviceroles.rbac.istio.io \
    templates.config.istio.io \
    virtualservices.networking.istio.io
   

3. Delete the istio-system namespace:

   kubectl delete ns istio-system