This page applies to Apigee, but not to Apigee hybrid.
View Apigee Edge documentation.
This page describes how to uninstall the Apigee APIM 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 APIM Operator for Kubernetes.
- Uninstall the Apigee CRDs.
Required roles
If you assigned the required roles to your service account as described in Install the Apigee APIM 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, see Authorize actions in clusters using role-based access control.
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 Use
Apigee policies with Apigee APIM Operator for Kubernetes,
you would remove the resources corresponding to the files in this order:
apim-policies.yaml
api-product.yaml
global-ext-lb1-apim-policy.yaml
Remove each resource using the following command:
kubectl delete -f FILENAME
Uninstall the Apigee APIM Operator for Kubernetes
To uninstall the Apigee APIM Operator for Kubernetes use the following commands:
helm uninstall apigee-apim-operator
helm repo remove apigee-apim-operator
These commands remove the Apigee APIM Operator for Kubernetes and the Apigee CRD Helm charts from your cluster.
Uninstall the CRDs
To uninstall the Apigee CRDs, use the following command:
helm uninstall apigee-apim-crds
Troubleshoot
If you encounter issues when uninstalling the Apigee APIM Operator for Kubernetes, see Troubleshoot the APIM Operator for solutions to common errors.