Cette page n'est pas encore disponible dans votre langue. Nous nous efforçons d'ajouter d'autres langues. Nous vous remercions de votre compréhension.
Application Service Mesh
Application Service Mesh
- What's New
- Service Overview
- Getting Started
- User Guide
- Best Practices
-
FAQs
- Service Mesh Cluster
- Mesh Management
-
Adding a Service
- What Do I Do If an Added Gateway Does Not Take Effect?
- Why Does It Take a Long Time to Start the Demo Application in Experiencing Service Mesh in One Click?
- Why Can't I Access the page of the Demo Application After It Is Successfully Deployed?
- Why Cannot I Select the Corresponding Service When Adding a Route?
- Performing Grayscale Release
- Videos
On this page
Help Center/
Application Service Mesh/
FAQs/
Service Mesh Cluster/
Why Does a Service Mesh Remain in the Unready Status for a Long Time After I Uninstall It?
Why Does a Service Mesh Remain in the Unready Status for a Long Time After I Uninstall It?
Updated on 2023-07-03 GMT+08:00
Description
On the ASM console, after I uninstall a service mesh, the mesh remains in the unready status for a long time.
Fault Diagnosis
- Log in to the CCE console, click the target cluster to go to its details page, and choose O&M > Charts in the navigation pane on the left.
- Click Releases and check the releases and the latest events about uninstallation failure.
The Status of istio-master is Uninstallation Failed, and the following message is displayed.
deletion failed with 1 error(s): clusterroles:rbac.authorization.k8s.io "istio-cleanup-secrets-istio-system" already exists
Analysis
Abnormal operations cause the Helm chart of Istio stuck during uninstallation. Residual resources lead to an uninstallation failure.
Solution
- Connect to the CCE cluster using kubectl.
- Run the following commands to clear Istio resources:
kubectl delete ServiceAccount -n istio-system `kubectl get ServiceAccount -n istio-system | grep istio | awk '{print $1}'` kubectl delete ClusterRole -n istio-system `kubectl get ClusterRole -n istio-system | grep istio | awk '{print $1}'` kubectl delete ClusterRoleBinding -n istio-system `kubectl get ClusterRoleBinding -n istio-system | grep istio | awk '{print $1}'` kubectl delete job -n istio-system `kubectl get job -n istio-system | grep istio | awk '{print $1}'` kubectl delete crd -n istio-system `kubectl get crd -n istio-system | grep istio | awk '{print $1}'` kubectl delete mutatingwebhookconfigurations -n istio-system `kubectl get mutatingwebhookconfigurations -n istio-system | grep istio | awk '{print $1}'` - Log in to the ASM console and uninstall the mesh again.
Parent topic: Service Mesh Cluster
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.
