Value Statement

this gets asked several times and the procedure does not work anymore without some modifications:
https://www.redhat.com/en/blog/how-your-grafana-can-fetch-metrics-from-red-hat-advanced-cluster-management-observability-observatorium-and-thanos

Also support scope needs to be clarified, e.g. we do not support external Grafana Dashboards.

Also the secret uses to connect is read-only

touch /tmp/external-grafana.txt
echo "# URL" > /tmp/external-grafana.txt
host=$(oc -n open-cluster-management-observability get route observatorium-api -o json | jq -r '.spec.host')
echo "https://${host}/api/metrics/v1/default" >> /tmp/external-grafana.txt
echo >> /tmp/external-grafana.txt

echo "# ca.crt" >> /tmp/external-grafana.txt
crt=$(oc -n open-cluster-management-observability get secret observability-server-ca-certs -o json | jq -r '.data."ca.crt"' | base64 -d )
echo "${crt}" >> /tmp/external-grafana.txt
echo >> /tmp/external-grafana.txt

echo "# client.crt" >> /tmp/external-grafana.txt
client_crt=$(oc -n open-cluster-management-observability get secret observability-grafana-certs -o json | jq -r '.data."tls.crt"'| base64 -d)
echo "${client_crt}" >> /tmp/external-grafana.txt
echo >> /tmp/external-grafana.txt

echo "# client.key" >> /tmp/external-grafana.txt
client_key=$(oc -n open-cluster-management-observability get secret observability-grafana-certs -o json | jq -r '.data."tls.key"' | base64 -d)
echo "${client_key}" >> /tmp/external-grafana.txt
echo >> /tmp/external-grafana.txt

plug those values into the datasource as per blog post

Definition of Done for Engineering Story Owner (Checklist)

• ...

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [ ] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [ ] The must-gather script has been updated.