*This page
applies to **Apigee** and **Apigee hybrid**.*


*View [Apigee Edge](https://docs.apigee.com/api-platform/get-started/what-apigee-edge) documentation.*
![](https://fonts.gstatic.com/s/i/googlematerialicons/help/v13/gm_grey-24dp/1x/gm_help_gm_grey_24dp.png)

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](https://docs.cloud.google.com/apigee/docs/api-platform/apigee-kubernetes/apigee-apim-operator-uninstall.md.txt#remove-policies).
- [Uninstall the Apigee Operator for Kubernetes](https://docs.cloud.google.com/apigee/docs/api-platform/apigee-kubernetes/apigee-apim-operator-uninstall.md.txt#uninstall-operator).
- [Uninstall the Apigee CRDs](https://docs.cloud.google.com/apigee/docs/api-platform/apigee-kubernetes/apigee-apim-operator-uninstall.md.txt#uninstall-crds).

<br />

## Required roles

If you assigned the required roles to your service account as described in [Install the Apigee Operator for Kubernetes](https://docs.cloud.google.com/apigee/docs/api-platform/apigee-kubernetes/apigee-apim-operator-install.md.txt#required-roles), 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, see [Authorize actions in clusters using role-based access control](https://docs.cloud.google.com/kubernetes-engine/docs/how-to/role-based-access-control.md.txt).

## Remove the API management policies

To remove the API management policies, remove all `yaml` Kubernetes resources applied to the GKE cluster in reverse order.
For example, if you followed the steps in [Create an `APIMExtensionPolicy`](https://docs.cloud.google.com/apigee/docs/api-platform/apigee-kubernetes/apigee-apim-operator-apimextension.md.txt) and [Add
policies to the GKE Gateway](https://docs.cloud.google.com/apigee/docs/api-platform/apigee-kubernetes/apigee-apim-operator-add-policies), 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:

```bash
kubectl delete -f FILENAME
```
where <var translate="no">FILENAME</var> is the name of the file corresponding to the resource you want to remove.

<br />

## Uninstall the Apigee Operator for Kubernetes

To uninstall the Apigee Operator for Kubernetes, use the following command:

```bash
helm uninstall apigee-apim-operator -n apim
```

This command removes the Apigee Operator for Kubernetes Helm chart from your cluster.

## Uninstall the CRDs

To uninstall the Apigee CRDs, use the following command:

```bash
helm uninstall apigee-apim-crds -n apim
```

## Troubleshoot

If you encounter issues when uninstalling the Apigee Operator for Kubernetes, see [Troubleshoot the Apigee Operator for Kubernetes](https://docs.cloud.google.com/apigee/docs/api-platform/apigee-kubernetes/apigee-apim-operator-troubleshoot.md.txt)
for solutions to common errors.