fix(perses): drop ready-state propagation, add explanatory note

kro v0.9.2 strips includeWhen-gated resources from the CEL context at
compile time, making it impossible to propagate their readiness into
status expressions. All workarounds tried (sentinel ConfigMap, ternary
expressions) either fail compilation or produce unreliable results.

status.ready is set to the static literal true in the Perses RGD.
A comment marks where real propagation would live and links to the
upstream issue. obs-stack.status.perses.ready is kept (removing it
would be a breaking CRD change) but is excluded from the ready gate.

See: kubernetes-sigs/kro#926 (comment)
Signed-off-by: Michael Sprauer <Michael.Sprauer@sap.com>

Author: MichaelSp

resource-graph-definitions/observability-stack.yaml

@@ -95,6 +95,9 @@ spec:
         ready: ${openTelemetryOperator.status.ready}
       openTelemetryCollector:
         ready: ${openTelemetryCollector.status.ready}
+      # NOTE: perses.ready is always true — kro v0.9.2 cannot propagate readiness
+      # from includeWhen-gated resources into status expressions.
+      # See: https://github.com/kubernetes-sigs/kro/issues/926#issuecomment-4313907502
       perses:
         ready: ${perses.status.ready}
       prometheusOperator:

resource-graph-definitions/perses.yaml

@@ -40,13 +40,11 @@ spec:
           limits:
             memory: string | default="512Mi"
             cpu: string | default="500m"
+    # NOTE: status.ready propagation is not implemented here.
+    # kro v0.9.2 removes includeWhen-gated resources from the CEL context at
+    # compile time, making it impossible to reference their status in expressions.
+    # See: https://github.com/kubernetes-sigs/kro/issues/926#issuecomment-4313907502
     status:
-      # kro v0.9.2 does not allow status expressions to reference resources gated
-      # by includeWhen (they are removed from the CEL context at compile time).
-      # Instance readiness is correctly gated by persesKustomization.readyWhen
-      # when enabled, and is vacuously true when disabled (excluded resources
-      # do not block instance readiness). status.ready is therefore always true.
-      # See: https://github.com/kubernetes-sigs/kro/issues/926#issuecomment-4313907502
       ready: true
       lastAttemptedRevisionDigest: ""