Problem

Installation is not straightforward enough for some users.

Suggestion

Use goreleaser (with a homebrew option for mac users, etc). The resulting installation section of your readme could then look something like [this](https://github.com/scottrigby/example-dep-no-vendor/#example-installati

Is your feature request related to a problem? Please describe.
Vault has backends for AWS like dynamo and s3. However to use them you should provide credentials. AWS support 2 solutions to eliminate this. IAM roles for Service Accounts and Instance profile roles.
Due to some unknown reason vault requires more time to start when using dynamic creds than explicit definition keys in s3 block o

Authentication via Azure/aad-pod-identity for keyvault access could be a good feature to avoid use of clientId/ clientSecret in chart values. Don't you think ?

Describe the solution you'd like

https://docs.microsoft.com/en-us/azure/aks/use-pod-security-policies
As you can see, pod security policy is getting deprecated on the 15th of October, superseded by Azure policies for AKS
https://docs.microsoft.com/en-us/azure/aks/use-pod-security-on-azure-policy
Since I use Azure policies for pods, I'd like if we update the [PSP definitions](https://raw.

It would be nice if there was an option to disable polling and offer an endpoint that could be called to force a sync so updates to secrets can be more controlled if desired.

Today the etcd example in CI is tagged on latest so it doesn't test the current branch in the pupernetes build.