Question about deleting old CRD

[BBQigniter]

Hello,

I have now tested the upgrade to v0.50.0 and also updated the CRDs via the job-manifest. After checking with

kubectl get crd -o name | grep kafka.strimzi.io | while read crd; do
  echo -n "$crd  "
  kubectl get "$crd" -o jsonpath='{.status.storedVersions}{"\n"}'
done

I got this output

customresourcedefinition.apiextensions.k8s.io/kafkabridges.kafka.strimzi.io  ["v1"]
customresourcedefinition.apiextensions.k8s.io/kafkaconnectors.kafka.strimzi.io  ["v1"]
customresourcedefinition.apiextensions.k8s.io/kafkaconnects.kafka.strimzi.io  ["v1"]
customresourcedefinition.apiextensions.k8s.io/kafkamirrormaker2s.kafka.strimzi.io  ["v1"]
customresourcedefinition.apiextensions.k8s.io/kafkamirrormakers.kafka.strimzi.io  ["v1beta2"]
customresourcedefinition.apiextensions.k8s.io/kafkanodepools.kafka.strimzi.io  ["v1"]
customresourcedefinition.apiextensions.k8s.io/kafkarebalances.kafka.strimzi.io  ["v1"]
customresourcedefinition.apiextensions.k8s.io/kafkas.kafka.strimzi.io  ["v1"]
customresourcedefinition.apiextensions.k8s.io/kafkatopics.kafka.strimzi.io  ["v1"]
customresourcedefinition.apiextensions.k8s.io/kafkausers.kafka.strimzi.io  ["v1"]

As MirrorMaker 1 support has been removed with v0.46.0 I assume I can just delete the old customresourcedefinition.apiextensions.k8s.io/kafkamirrormakers.kafka.strimzi.io CRD. Also we do not use mirror-stuff - so I executed kubectl delete customresourcedefinition.apiextensions.k8s.io/kafkamirrormakers.kafka.strimzi.io - now I only wonder if it's normal that deleting an old unused CRD takes several minutes? Or should I be concerned now that something is wrong (the logs are looking ok as far as i have seen)?

[scholzj]

Yes, as long as you don't use any older Strimzi versions (for example, in some other namespaces), you can delete it. The CRD deletion is sometimes slow, although several minutes seem a bit too much. But I do not think it has to indicate sme kind of problem.

[BBQigniter]

thank you - all clear to me now 😄