pagetron is deploying.

{{ if and .Values.publicAccess.httpRoute.enabled .Values.publicAccess.ingress.enabled -}}
WARNING

    publicAccess.httpRoute.enabled and publicAccess.ingress.enabled are both true,
    so {{ include "pagetron.publicHost" . }} is served by an HTTPRoute and an Ingress at
    once. That is fine during a cutover, but turn one off once you are done.

{{ end -}}
{{ if .Values.publicAccess.httpRoute.enabled -}}
Traffic reaches pagetron through an HTTPRoute attached to:
{{ range .Values.publicAccess.httpRoute.gateways }}
    {{ .kind | default "Gateway" }} {{ .namespace }}/{{ .name }}
{{- end }}

TLS is not configured by this chart - that Gateway's listener terminates it and owns
the certificate for {{ include "pagetron.publicHost" . }}.

{{ end -}}
{{ if .Values.prometheus.enabled -}}
Metrics come from the Prometheus bundled with this chart.
{{- else if .Values.prometheus.operator.enabled -}}
Metrics come from your existing in-cluster Prometheus at:

    {{ .Values.prometheusUrl }}

A Probe (pagetron-targets) and a PrometheusRule (pagetron-availability) were created
for it to pick up. If the status page stays empty, that Prometheus is most likely not
selecting them - check its probeSelector and ruleSelector against:

    prometheus.operator.labels: {{ .Values.prometheus.operator.labels | toJson }}

Also note the quarter and year views need ~1y of retention on that Prometheus. The
usual 10-15d default renders them as gaps.
{{- else -}}
WARNING

    prometheus.enabled and prometheus.operator.enabled are both false, so nothing
    this chart deploys produces the pagetron:availability:{1m,1h,1d} series the
    backend reads. The status page will stay empty unless you have set up those
    recording rules on {{ .Values.prometheusUrl }} yourself.

    Set prometheus.operator.enabled: true to have the chart ship them as a
    PrometheusRule, or see README, "Using an existing in-cluster Prometheus".
{{- end }}
