AI Agents

  • Fixed

    Full Changelog: https://github.com/giantswarm/klaus/compare/v0.1.38...v0.1.39

  • Fixed

    • (deps) Update module github.com/giantswarm/selfupdate-cosign to v0.3.1 in #507 by @renovate[bot]

    Full Changelog: https://github.com/giantswarm/klaus/compare/v0.1.37...v0.1.38

  • Fixed

    • muster test: instance_logs see the lines background work logs after the last step. The runner read the running instance’s output once, right after the last step answered, so a line logged by work a call started in the background – the core catalogue’s age-triggered rebuild – or still in the capture pipe was missing on a loaded CI machine, and workflow-catalogue-age-refresh-on-production-schedule failed on main with the rebuild counted on 0 lines. While a contains substring is missing or an occurrences count is below its value, the runner now keeps reading the output for up to ten seconds before it evaluates the block; a not_contains hit or an exceeded count is reported at once.
  • Changed

    • Publish latest from the tag pipeline, not from main in #511 by @teemow

    Full Changelog: https://github.com/giantswarm/klaus/compare/v0.1.36...v0.1.37

  • Added

    • The data plane traces a share of the requests that arrive with no trace context: gateway.tracing.randomSampling, 0.1, on the <release>-tracing AgentgatewayPolicy (frontend.tracing.randomSampling) (giantswarm/giantswarm#36711). Before, the data plane traced only requests with a sampled traceparent, so an MCP client such as Claude Code through muster got no data-plane span. The value is a number between 0 and 1 or a boolean; empty or 0 turns random sampling off and keeps the export of traced requests. A request with an unsampled traceparent stays untraced. The span metrics of service="agentgateway" now mix all traced requests with this share of the others; agentgateway_requests_total stays the source for rates. make verify-dataplane-tracing asserts the value, the overrides, the schema and the meta chart’s forwarding. Both charts carry the default. README “The data plane’s traces”.
  • Fixed

    • Substrate’s OTLP export reaches the collector with a tenant: substrate.podLabels and the connectivity chart’s Substrate egress follow substrate.otel (giantswarm/giantswarm#36711). The meta chart sets substrate.podLabels to observability.giantswarm.io/tenant: giantswarm, the label otlp-gateway routes a headerless export by; the substrate chart takes the key from the line’s 1.1.0 (giantswarm/substrate#55, carrying kagent-dev/substrate#48), an older release ignores it. The substrate-ate-api-server, -ate-controller, -atelet and -atenet-router Cilium policies open the namespace and port of each enabled signal’s endpoint (agent-platform.substrate.otlpEgress); ate-api-server’s fixed rule to the cluster entity on 4317 is gone, and no endpoint opens nothing. Trace sampling stays at the chart’s parentbased_traceidratio 0.01. make verify-substrate-otlp asserts it. Every installation with Substrate on gets the four changed policies; the Substrate pods roll once on the upgrade to 1.1.0 (the pod label).
  • Fixed

    • The Overview’s Valkey memory used stat and Memory used against the limit panel divide each Valkey’s used memory by its own maxmemory (giantswarm/giantswarm#36711). Both divided the highest usage in a namespace by the highest bound, which can come from different instances: agent-platform runs muster-valkey next to an unbounded Valkey of another release. The panel draws one line per instance (job) instead of one per namespace, the same grouping as AgentPlatformValkeyMemoryHigh (giantswarm/prometheus-rules#2183).
  • Changed

    Full Changelog: https://github.com/giantswarm/klausctl/compare/v0.4.16...v0.4.17

  • Changed

    Full Changelog: https://github.com/giantswarm/muster/compare/v5.32.0...v5.32.1

  • Changed

    Fixed

    Full Changelog: https://github.com/giantswarm/klaus-operator/compare/v0.0.171...v0.0.172