Questa pagina descrive come disinstallare l'operatore Apigee APIM per Kubernetes da un cluster GKE. Le sezioni seguenti
descrivono i passaggi necessari per completare questa attività:
Se hai assegnato i ruoli richiesti al account di servizio come descritto in
Installare l'operatore Apigee APIM per Kubernetes, non sono necessari ruoli o autorizzazioni IAM aggiuntivi per completare queste attività.
Questi comandi rimuovono l'operatore Apigee APIM per Kubernetes e i grafici Helm CRD Apigee dal cluster.
Disinstallare i CRD
Per disinstallare le CRD Apigee, utilizza il seguente comando:
helmuninstallapigee-apim-crds-napim
Risoluzione dei problemi
Se riscontri problemi durante la disinstallazione dell'operatore APIM di Apigee per Kubernetes, consulta la sezione Risoluzione dei problemi dell'operatore APIM
per trovare soluzioni agli errori comuni.
[[["Facile da capire","easyToUnderstand","thumb-up"],["Il problema è stato risolto","solvedMyProblem","thumb-up"],["Altra","otherUp","thumb-up"]],[["Difficile da capire","hardToUnderstand","thumb-down"],["Informazioni o codice di esempio errati","incorrectInformationOrSampleCode","thumb-down"],["Mancano le informazioni o gli esempi di cui ho bisogno","missingTheInformationSamplesINeed","thumb-down"],["Problema di traduzione","translationIssue","thumb-down"],["Altra","otherDown","thumb-down"]],["Ultimo aggiornamento 2025-09-05 UTC."],[[["\u003cp\u003eThis guide explains how to uninstall the Apigee APIM Operator for Kubernetes from a GKE cluster, specifically for Apigee, and not Apigee hybrid.\u003c/p\u003e\n"],["\u003cp\u003eUninstalling involves removing API management policies, the Apigee APIM Operator, and the Apigee CRDs in a specific order.\u003c/p\u003e\n"],["\u003cp\u003eAPI management policies must be removed in reverse order of their application using the \u003ccode\u003ekubectl delete -f FILENAME\u003c/code\u003e command.\u003c/p\u003e\n"],["\u003cp\u003eThe Apigee APIM Operator and its CRD Helm charts are removed using \u003ccode\u003ehelm uninstall\u003c/code\u003e commands.\u003c/p\u003e\n"],["\u003cp\u003eTroubleshooting for common issues during uninstallation is available in the APIM Operator troubleshooting guide.\u003c/p\u003e\n"]]],[],null,["# Uninstall the Apigee APIM Operator for Kubernetes\n\n*This page\napplies to **Apigee** , but not to **Apigee hybrid**.*\n\n\n*View [Apigee Edge](https://docs.apigee.com/api-platform/get-started/what-apigee-edge) documentation.*\n\nThis page describes how to uninstall the Apigee APIM Operator for Kubernetes from a GKE cluster. The following sections\noutline the steps required to complete this task:\n\n- [Remove the API management policies](#remove-policies).\n- [Uninstall the Apigee APIM Operator for Kubernetes](#uninstall-operator).\n- [Uninstall the Apigee CRDs](#uninstall-crds).\n\n\u003cbr /\u003e\n\nRequired roles\n--------------\n\nIf you assigned the required roles to your service account as described in [Install the Apigee APIM Operator for Kubernetes](/apigee/docs/api-platform/apigee-kubernetes/apigee-apim-operator-install#required-roles), no additional IAM roles or permissions are required to complete these tasks.\n\nYou can choose to authorize actions on resources in your Google Kubernetes Engine cluster using the built-in role-based access control (RBAC)\nmechanism in Kubernetes. For more information, see [Authorize actions in clusters using role-based access control](/kubernetes-engine/docs/how-to/role-based-access-control).\n\nRemove the API management policies\n----------------------------------\n\nTo remove the API management policies, remove all `yaml` Kubernetes resources applied to the GKE cluster in reverse order.\nFor example, if you followed the steps in [Use API management policies with the\nApigee APIM Operator for Kubernetes](/apigee/docs/api-platform/apigee-kubernetes/apigee-apim-operator-create) and [Add\npolicies to the GKE Gateway](/apigee/docs/api-platform/apigee-kubernetes/apigee-apim-operator-add-policies), you would remove the resources corresponding to the files in this order:\n\n- `apigee-gateway-policy-withSA.yaml`\n- `new-admin-template.yaml`\n- `template-rule.yaml`\n- `apigee-policies.yaml`\n- `apim-policies.yaml`\n- `api-product.yaml`\n- `global-ext-lb1-apim-policy.yaml`\n\nRemove each resource using the following command: \n\n```bash\nkubectl delete -f FILENAME\n```\nwhere \u003cvar translate=\"no\"\u003eFILENAME\u003c/var\u003e is the name of the file corresponding to the resource you want to remove.\n\n\u003cbr /\u003e\n\nUninstall the Apigee APIM Operator for Kubernetes\n-------------------------------------------------\n\nTo uninstall the Apigee APIM Operator for Kubernetes use the following commands: \n\n helm uninstall apigee-apim-operator -n apim\n helm repo remove apigee-apim-operator\n\nThese commands remove the Apigee APIM Operator for Kubernetes and the Apigee CRD Helm charts from your cluster.\n\nUninstall the CRDs\n------------------\n\nTo uninstall the Apigee CRDs, use the following command: \n\n```bash\nhelm uninstall apigee-apim-crds -n apim\n```\n\nTroubleshoot\n------------\n\nIf you encounter issues when uninstalling the Apigee APIM Operator for Kubernetes, see [Troubleshoot the APIM Operator](/apigee/docs/api-platform/apigee-kubernetes/apigee-apim-operator-troubleshoot)\nfor solutions to common errors."]]
