Fluentdconfig object deleted, pod is still running

[OverOrion]

Bugs should be filed for issues encountered whilst operating logging-operator.
You should first attempt to resolve your issues through the community support
channels, e.g. Slack, in order to rule out individual configuration errors. #logging-operator
Please provide as much detail as possible.

Describe the bug:
Fluentdconfig object deleted but the pod is still running

Expected behaviour:
Fluentdconfig object deletion should stop the currently running pod.

Steps to reproduce the bug:
Dispatch a fluentdconfig (or use the e2e test case), delete the fluentdconfig object and the pod is still there.

Additional context:
logging.Status.FluentdConfigName can be used to decide whether a fluentdconfig:

• does not exist YET (.Status.FluentdConfigName is not set)
• NO LONGER exists (.Status.FluentdConfigName is set, but object is not there)

Questions:

• If a fluentdconfig gets deleted should be owning loggingspec be reusable for a different one?

Maybe weak references could help here?

Environment details:

• Kubernetes version (e.g. v1.15.2):
• Cloud-provider/provisioner (e.g. AKS, GKE, EKS, PKE etc):
• logging-operator version (e.g. 2.1.1):
• Install method (e.g. helm or static manifests):
• Logs from the misbehaving component (and any other relevant logs):
• Resource definition (possibly in YAML format) that caused the issue, without sensitive data:

/kind bug