Handling of updated secrets and configuration

[dmacvicar]

In the CNLC branch, if a secret is updated, kube-notary does not realize it, as it is exposed as an environment variable.

• https://kubernetes.io/docs/concepts/configuration/secret/#environment-variables-are-not-updated-after-a-secret-update

The behavior of KubeNotary should be examined and a decision needs to be made how to handle (or document this case).

As Kubernetes does not appear to provide a solution, unless you use eg. mounted secrets, or Helm tricks, the solution may very well to ignore the problem and document it properly.
If the route of making kube-notary aware of the changes is chosen, it needs to be something in line of how Kubernetes workloads usually deal with this.