This pageapplies toApigee andApigee hybrid.

View Apigee Edge documentation.

This page describes how to uninstall the Apigee Operator for Kubernetes from a GKE cluster. The following sections outline the steps required to complete this task:

• Remove the API management policies.
• Uninstall the Apigee Operator for Kubernetes.
• Uninstall the Apigee CRDs.

Required roles

If you assigned the required roles to your service account as described inInstall the Apigee Operator for Kubernetes, no additional IAM roles or permissions are required to complete these tasks.

You can choose to authorize actions on resources in your Google Kubernetes Engine cluster using the built-in role-based access control (RBAC)mechanism in Kubernetes. For more information, seeAuthorize actions in clusters using role-based access control.

Remove the API management policies

To remove the API management policies, remove allyaml Kubernetes resources applied to the GKE cluster in reverse order.For example, if you followed the steps inCreate anAPIMExtensionPolicy andAdd policies to the GKE Gateway, you would remove the resources corresponding to the files in this order:

• apigee-gateway-policy-withSA.yaml
• new-admin-template.yaml
• template-rule.yaml
• apigee-policies.yaml
• apim-policies.yaml
• api-product.yaml
• global-ext-lb1-apim-policy.yaml

Remove each resource using the following command:

kubectldelete-fFILENAME

Uninstall the Apigee Operator for Kubernetes

To uninstall the Apigee Operator for Kubernetes use the following commands:

helmuninstallapigee-apim-operator-napimhelmreporemoveapigee-apim-operator

These commands remove the Apigee Operator for Kubernetes and the Apigee CRD Helm charts from your cluster.

Uninstall the CRDs

To uninstall the Apigee CRDs, use the following command:

helmuninstallapigee-apim-crds-napim

Troubleshoot

If you encounter issues when uninstalling the Apigee Operator for Kubernetes, seeTroubleshoot the Apigee Operator for Kubernetes for solutions to common errors.