[kube-prometheus-stack] How to use oauth2-proxy sidecars to add oauth2 over prometheus & alertmanager

[rgarrigue]

Describe the bug a clear and concise description of what the bug is.

The chart's values.yaml got around here a comment suggesting that alertmanager (& prometheus laterin the file) can have a sidecar configured to add oauth2-proxy based oauth over AM & Prom.

    ## Containers allows injecting additional containers. This is meant to allow adding an authentication proxy to an Alertmanager pod.
    ##
    containers: []
    # containers:
    # - name: oauth-proxy
    #   image: quay.io/oauth2-proxy/oauth2-proxy:v7.3.0
    #   args:
    #   - --upstream=http://127.0.0.1:9093
    #   - --http-address=0.0.0.0:8081
    #   - ...
    #   ports:
    #   - containerPort: 8081
    #     name: oauth-proxy
    #     protocol: TCP
    #   resources: {}

Anyone can provide a functional example of the above ?

What's your helm version?

3.9.3

What's your kubectl version?

1.24.2

Which chart?

prometheus-kube-stack

What's the chart version?

47.6.1

What happened?

No response

What you expected to happen?

No response

How to reproduce it?

No response

Enter the changed values of values.yaml?

No response

Enter the command that you execute and failing/misfunctioning.

ArgoCD's running helm upgrade --install ... for me

Anything else we need to know?

I'm using Google for OAuth2 & Contour as an ingress controller. But I'll manage to adapt provided a functional example with other 3rd parties.

[stale[bot]]

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.

[ghost]

Any update? There is no proper docs. I am trying to configure it but with no luck

[stale[bot]]

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[bot]]

This issue is being automatically closed due to inactivity.