Uploaded image for project: 'OpenShift Monitoring'
  1. OpenShift Monitoring
  2. MON-3381

Replace oauth-proxy container with kube-rbac-proxy in Alertmanager pods

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • None
    • Alertmanager
    • None
    • MON Sprint 250

      In CMO, Alertmanager pods in the openshift-monitoring namespace have an Oauth-proxy on port 9095 for web access on all paths.

      We are going to replace it with kube-rbac-proxy and constraint the access to /api/v2 pathes. 

      The current behavior is to allow access to the Alertmanager web server for any user having "get" access to "namespace" resources. We do not have to keep the same logic but have to make sure no regression happen. We may need use a stubbed custom resource to authorize both "post" and "get" HTTP requests from certain users.

      There is a request to allow read-only access to alerts in Developer view. kube-rbac-proxy can facilitate this functionality.

              spasquie@redhat.com Simon Pasquier
              hasun@redhat.com Haoyu Sun
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: