Adjust Prometheus http readiness probe path from /status to /-/ready

Prometheus documentation shows that /-/ready can be used to check that
it is ready to service traffic (i.e. respond to queries) [0]. I've
witnessed cases where Prometheus's readiness probe is passing during
initial deployment using /status, which in turn triggers its helm test
to start. Said helm test then fails because /status is not a good a
reliable indicator that Prometheus is actually ready to serve traffic
and the helm test is performing actions that require it to be proprely
up and ready.

[0]: https://prometheus.io/docs/prometheus/latest/management_api/

Change-Id: Iab22d0c986d680663fbe8e84d6c0d89b03dc6428

prometheus/Chart.yaml

@@ -15,7 +15,7 @@ apiVersion: v1
 appVersion: v2.25.0
 description: OpenStack-Helm Prometheus
 name: prometheus
-version: 0.1.7
+version: 0.1.8
 home: https://prometheus.io/
 sources:
   - https://github.com/prometheus/prometheus

prometheus/templates/statefulset.yaml

@@ -18,7 +18,7 @@ limitations under the License.
 {{- $probePass := .Values.endpoints.monitoring.auth.admin.password }}
 {{- $authHeader := printf "%s:%s" $probeUser $probePass | b64enc }}
 httpGet:
-  path: /status
+  path: /-/ready
   scheme: {{ tuple "monitoring" "internal" "api" . | include "helm-toolkit.endpoints.keystone_endpoint_scheme_lookup" | upper }}
   port: {{ $probePort }}
   httpHeaders:

releasenotes/notes/prometheus.yaml

@@ -8,4 +8,5 @@ prometheus:
   - 0.1.5 Fix spacing inconsistencies with flags
   - 0.1.6 Upgrade version to v2.25 fix/remove deprecated flags
   - 0.1.7 Enable TLS for Prometheus
+  - 0.1.8 Change readiness probe from /status to /-/ready
 ...