Reload Configuration only when a pod matching the label set in mounted-file is created or deleted

[huskykurt]

According to the issue comments (comment1, comment2) the existing solution caused too many configuration reloads.
This is because the configuration reload occurred whenever every pod was created (or deleted). So it is not affordable for a large cluster.
So, make the configuration reload only when a pod with the label set in the mounted-file is created (or deleted).

[huskykurt]

Hello @javiercri. How do I get a review for this PR? I looked at the CLA FAQ and they said that if I send a PR, I will receive a comment requesting the CLA, but there is no comment.

[javiercri]

First sorry for the late reply.
Could you fix the conflicts here @huskykurt, and I can approve it.
Thanks in advance!

[vmwclabot]

@huskykurt, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit f0131e0 must be signed by [email protected]

[vmwclabot]

@huskykurt, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit f0131e0 must be signed by [email protected]

[huskykurt]

First sorry for the late reply. Could you fix the conflicts here @huskykurt, and I can approve it. Thanks in advance!

That's OK. I fixed the conflicts.

[javiercri]

LGTM