[aws-sigv4-proxy-admission-controller] Adding Mechanism to Avoid Deadlock

[wjhhuizi]

Issue

#822 Avoiding Deadlock in aws-sigv4-proxy-admission-controller Chart.

Description of changes

Adding an objectSelector to avoid webhook lock it self out in case of crashing or evicting situation.
This will allow webhook to skip applying mutation webhhok on pods with lable app: {{ template "aws-sigv4-proxy-admission-controller.fullname" . }}

Checklist

• Added/modified documentation as required (such as the README.md for modified charts)
• Incremented the chart version in Chart.yaml for the modified chart(s)
• Manually tested. Describe what testing was done in the testing section below
• Make sure the title of the PR is a good description that can go into the release notes

Testing

Manually deployed modified Chart and the pod can now avoid locking itself out after crashing/evicting/scaling event.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[butlern]

I just ran into this issue when creating the sigv4 deployment with this chart. It was installing the webhook config before the deployment and the deployment was failing to launch due to needing to hit the webhook admission endpoint which was managed by the deployment... Would be great to see this merged. 👍

[guitmz]

this is still happening after 1 year...

edit: the fix is not working for me 100% though. It does make the pod able to restart but I still see the consequences of #672 on any new pod that tries to start