How Can I Clean Up Residual Resources After the NGINX Ingress Controller Add-on in the Unknown State Is Deleted?
Symptom
The NGINX Ingress Controller add-on is in the unknown state, and after this add-on is uninstalled, residual components still remain.
Involved Kubernetes resources include:
- Namespace-level resources: secret, ConfigMap, Deployment, Service, Role, RoleBinding, lease, ServiceAccount, and job
- Cluster-level resources: ClusterRole, ClusterRoleBinding, IngressClass, and ValidatingWebhookConfiguration
Solution
- Use kubectl to access a cluster.
- Search for related resources.
className="nginx" namespace="kube-system" className=`if [[ ${className} == "nginx" ]]; then echo ""; else echo "-${className}";fi` kubectl get -n ${namespace} secret sh.helm.release.v1.cceaddon-nginx-ingress${className}.v1 cceaddon-nginx-ingress${className}-admission kubectl get -n ${namespace} cm cceaddon-nginx-ingress${className}-controller kubectl get -n ${namespace} deploy cceaddon-nginx-ingress${className}-controller cceaddon-nginx-ingress${className}-default-backend kubectl get -n ${namespace} svc cceaddon-nginx-ingress${className}-controller-admission cceaddon-nginx-ingress${className}-default-backend cceaddon-nginx-ingress${className}-controller kubectl get -n ${namespace} role cceaddon-nginx-ingress${className} kubectl get -n ${namespace} rolebinding cceaddon-nginx-ingress${className} kubectl get -n ${namespace} lease ingress-controller-leader${className} kubectl get -n ${namespace} serviceAccount cceaddon-nginx-ingress${className} kubectl get clusterRole cceaddon-nginx-ingress${className} kubectl get clusterRoleBinding cceaddon-nginx-ingress${className} kubectl get ingressClass ${className} kubectl get ValidatingWebhookConfiguration cceaddon-nginx-ingress${className}-admission
className specifies the name of a controller. namespace specifies the namespace where NGINX Ingress Controller was installed.
- Manually delete the residual resources if the preceding resources are present.
Chart and Add-on FAQs
- What Should I Do If the nginx-ingress Add-on Fails to Be Installed on a Cluster and Remains in the Creating State?
- What Should I Do If Residual Process Resources Exist Due to an Earlier npd Add-on Version?
- What Should I Do If a Chart Release Cannot Be Deleted Because the Chart Format Is Incorrect?
- Does CCE Support nginx-ingress?
- Why Does Add-on Installation Fail and Prompt "The release name is already exist"?
- What Should I Do If a Release Creation or Upgrade Fails and "rendered manifests contain a resource that already exists" Is Displayed?
- What Should I Do If a kube-prometheus-stack Pod Fails to Be Scheduled and the Message "node(s) had volume node affinity conflict" Is Displayed?
- What Should I Do If a Chart Fails to Be Uploaded?
- How Do I Configure the Add-on Resource Quotas Based on Cluster Scale?
- How Can I Clean Up Residual Resources After the NGINX Ingress Controller Add-on in the Unknown State Is Deleted?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore