agent-platform release v4.57.1

gpu-operator.dcgmExporter.serviceMonitor.additionalLabels carries the tenant label (giantswarm/giantswarm#36711). The upstream chart turns the DCGM exporter’s ServiceMonitor on by default with additionalLabels: {}, and this chart forwarded nothing to fill it, so an installation that enables components.gpu-operator would scrape GPU metrics into no tenant and report no error — the failure klaus-gateway had before agent-platform#621. gpu-operator.dcgmExporter.serviceMonitor.additionalLabels."observability.giantswarm.io/tenant" is giantswarm. No installation runs this component yet, so nothing changes until one does.

muster’s OTLP export reaches the collector: the connectivity chart renders -muster-otlp-egress (giantswarm/giantswarm#36711). muster’s own network policy (muster sub-chart) allows egress to the cluster entity on 80/443 only, so with muster.muster.observability.otel.endpoint set every export was dropped at the SYN, and no muster span or OTLP log reached Tempo or Loki. The new policy selects muster by name and allows DNS plus the endpoint’s namespace on its port (the cluster entity for a host that is not an in-cluster Service), in both policy flavours, through the same agent-platform.otlpTarget / agent-platform.otlpEgressRule helpers as -klausgateway-otlp-egress. It renders exactly while the endpoint is set, with networkPolicy.enabled and the muster component on. make verify-muster-otlp asserts it. Every installation with muster on gets one new object; no pod rolls.