Fluentbit pods don't restart when new Eleastic cluster is deployed

During an install of BigBang the following occured:

1. Install of Umbrella
2. Deletion of Elasticsearch CR
3. Recreation of Elasticsearch CR via helm controller

At this point, fluentbit was running with the secret from the original deployment of 1) and did not re-start with the new secrets from the elastic search created in 3).