oauth-proxy fronting AlertManager

[davidkirwan]

JIRA: https://issues.jboss.org/browse/INTLY-619

AlertManager: Add OAuth Proxy login so the various consoles are not accessible to unauthenticated users.

Verification steps on integreatly cluster:

• In the application-monitoring-operator directory on this branch:

oc new-project application-monitoring
oc label namespace application-monitoring monitoring-key=middleware
oc apply -f https://raw.githubusercontent.com/integr8ly/grafana-operator/master/deploy/crds/Grafana.yaml
oc apply -f https://raw.githubusercontent.com/integr8ly/grafana-operator/master/deploy/crds/GrafanaDashboard.yaml
oc apply -f ./deploy/roles
oc apply -f ./deploy/operator_roles/
oc apply -f ./deploy/crds/ApplicationMonitoring.yaml
oc apply -f ./deploy/operator.yaml
oc apply -f ./deploy/examples/ApplicationMonitoring.yaml

• Scale down the Application Monitoring Operator in the "Managed Service Monitoring" namespace, and scale down the Application Monitoring Operator in the "application monitoring" namespace
• Run the Application monitoring Operator locally operator-sdk up local --namespace application-monitoring
• Delete the ApplicationMonitoring custom resource: oc delete applicationmonitorings example-applicationmonitoring -n application-monitoring
• Redeploy everything oc apply -f ./deploy/examples/ApplicationMonitoring.yaml -n application-monitoring using the operator running locally
• Once finished, expect to see unique values in the following secrets: prometheus-k8s-proxy
• Logging into the AlertManager dashboard should allow you to authenticate via openshift and prevent you accessing the dashboard otherwise

[davidkirwan]

I think I'm going to have to add a change to the upgrade playbook to handle this port change.