Curator Component [ cm,cronjob,pod] exists even after deleting from cluster logging CR

What is the problem that your customer is facing?

Curator Component [ cm,cronjob,pod] exists even after deleting from cluster logging CR

What is the business impact, if any, if this request will not be made

available?

What are your expectations for this feature

Curator component this should be automatically deleted once we delete the Curator section from CR

Have you done this before and/or outside of support and if yes, how?

(Optional)
Steps to reproduce :

1) create/apply CR with a curator section
2) observe that a curator job and config map is created
3) delete the config on curator in the CR
4) observe that the job and configmap is still there