[stable/oauth2-proxy] Upgrade to 5.0+ to resolve security issue

[jeremyolliver]

Hi, I noticed on the README at https://github.com/pusher/oauth2_proxy#security that there's an open redirect vulnerability which requires running oauth2-proxy 5.0+ to resolve. The latest version in this chart to date runs 4.0 - I'd like to continue running the official stable helm chart that packages this, but it's important that this contains available security fixes. I'm not yet sure if I'll have time to submit a PR, so I wanted to file this to track the issue first.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

[stale]

This issue is being automatically closed due to inactivity.

[abdennour]

Not sure why these bots are closed many valid issues.

@jeremyolliver do you get any workaround ?
Many things are outdated when we check the official software doc

• The image repo is now quay.io/oauth2-proxy/oauth2-proxy, and No more quay.io/pusher/oauth2-proxy
• processing .Values.extraArgs in templates/deployment.yam is outdated.
  Indeed, All args are now started by - not --.

....