Custom CRDs not getting deleted in aks cluster, how to delete that?

Question

Custom CRDs not getting deleted in aks cluster, how to delete that?

Uday Kiran Reddy (ureddy) 96

I have installed consul helm repository to default namespace. Now, want to change it to a custom namespace.

So, deleted the help chart using helm uninstall command. Now, when I try to install again, getting error as CRDs are already configured earlier, need to cleanup them.

So, ran the below command to check the CRDs.

kubectl get CustomResourceDefinition --all-namespaces
NAME CREATED AT
healthstates.azmon.container.insights 2021-09-24T14:19:01Z
ingressgateways.consul.hashicorp.com 2021-09-26T13:17:13Z
servicedefaults.consul.hashicorp.com 2021-09-26T13:17:13Z
serviceintentions.consul.hashicorp.com 2021-09-26T13:17:13Z
servicerouters.consul.hashicorp.com 2021-09-26T13:17:13Z

The above CRDs, I need to cleanup all with consul as subtext.

So, I tried deleting one by one.But it got stuck there without deleting them when I ran any command below.

kubectl delete crd serviceintentions.consul.hashicorp.com
customresourcedefinition.apiextensions.k8s.io "serviceintentions.consul.hashicorp.com" deleted

I waited for 1 hour, but no response so entered ctrl+c to cancel and ran get command again, seems they are not deleted.

Please suggest how to fix this?

SRIJIT-BOSE-MSFT 4,346 Reputation points Microsoft Employee

2021-10-25T09:00:53.48+00:00
Can you please perform a kubectl get crd -A -o jsonpath='{.items[*].metadata.finalizers' to check if the delete operation is in deadlock with finalizers set on the CRDs?

In that case, you can perform the following:

kubectl patch crd <custome-resource-definition-name> -n <namespace> -p '{"metadata":{"finalizers":[]}}' --type=merge kubectl delete crd <custome-resource-definition-name> -n <namespace>
Uday Kiran Reddy (ureddy) 96 Reputation points

2021-10-25T09:03:03.71+00:00

empty list
Uday Kiran Reddy (ureddy) 96 Reputation points

2021-10-25T09:08:55.387+00:00

Even when I try, I am getting as invalid JSON Patch

kubectl patch crd ingressgateways.consul.hashicorp.com -p '{"metadata":{"finalizers":[]}}' --type=merge
Error from server: Invalid JSON Patch

1 answer

Your answer

SRIJIT-BOSE-MSFT 4,346 Reputation points Microsoft Employee

2021-10-25T09:00:53.48+00:00

Can you please perform a kubectl get crd -A -o jsonpath='{.items[*].metadata.finalizers' to check if the delete operation is in deadlock with finalizers set on the CRDs?

In that case, you can perform the following:

kubectl patch crd <custome-resource-definition-name> -n <namespace> -p '{"metadata":{"finalizers":[]}}' --type=merge kubectl delete crd <custome-resource-definition-name> -n <namespace>
Uday Kiran Reddy (ureddy) 96 Reputation points

2021-10-25T09:03:03.71+00:00

empty list
Uday Kiran Reddy (ureddy) 96 Reputation points

2021-10-25T09:08:55.387+00:00

Even when I try, I am getting as invalid JSON Patch

kubectl patch crd ingressgateways.consul.hashicorp.com -p '{"metadata":{"finalizers":[]}}' --type=merge
Error from server: Invalid JSON Patch

Answer 1

Uday Kiran Reddy (ureddy) 96

Applying the patch command didn't work.
So, I manually edited the CRD by using below command and deleted the finalizer section fromt he CRDs, then it got deleted directly.

kubectl edit crd <CRD-Name>

Thank you very much for your reply.
Also, can you suggest, how to rename a cluster in azure kubernetes, either through portal or any API Command, whichever is possible

SRIJIT-BOSE-MSFT 4,346 Reputation points Microsoft Employee

2021-10-25T10:51:03.807+00:00

@Uday Kiran Reddy (ureddy) , thank you for posting your answer. This will definitely help others in the community looking for answers on similar topics.

At the time of writing, you cannot change the name of an AKS cluster after creation. For an AKS cluster with a new name you have to redeploy the AKS cluster. [Reference]

Share via

Custom CRDs not getting deleted in aks cluster, how to delete that?

1 answer

Your answer