Changes and Releases
Updates on Giant Swarm workload cluster releases, apps, UI improvements and documentation changes.
Fixed
- A client connection through a gateway survives a replaced aggregator pod. For a while after muster’s pod was replaced, the gateway in front of it answered
upstream call failed: Connect: deadline has elapsed, and every CLI command failed with failed to connect to aggregator on the first such answer, although the new pod was healthy. The agent client’s Connect now retries a connection that did not reach the aggregator (a refused, reset or timed-out connection, or a gateway’s 502, 503, 504 or failed upstream call) with a fresh session for up to 30 seconds, bounded by the caller’s context; a 401 or any other refusal is final. muster auth token prints a valid stored access token without contacting the aggregator and connects only to renew an expired one. (#1536)
Fixed
- The chart takes an
affinity. values.schema.json declared affinity as an object with no properties allowed, so every affinity a deployment set, a pod anti-affinity spreading two replicas over nodes for one, failed the install with Additional property podAntiAffinity is not allowed. The key now accepts any affinity, like nodeSelector. (giantswarm/agent-platform#1080)
Changed
- The portal moves to the backstage 3.x line, the Agent Platform shell (giantswarm/agent-platform#1067).
components.backstage.versionRange is >=2.68.0 <4.0.0, so the portal resolves the latest 3.x release, the shell with the connectors’ display names, without an own range or a patched Deployment. 3.0.0 changes the portal’s UI, not its chart values; the connectivity chart’s app-config already turns the shell on (app.portals.agentPlatform). An installation that keeps the classic portal sets components.backstage.versionRange: ">=2.68.0 <3.0.0".
Changed
Fixed
- (helm) MCPServer alerts leave out person-registered servers in #1530 by @teemow
- (metatools) Rank filter_tools queries over the full description in #1537 by @marians
Full Changelog: https://github.com/giantswarm/muster/compare/v5.43.4...v5.43.5
Fixed
- (agent-platform) Answer 404, not 502, for avatars of an installation that serves none by @teemow — For operators: on an installation that serves no agent avatars, the portal’s avatar requests answer 404, as for an agent without one, instead of a 502 and a logged bad gateway per image on every page listing agents.
- (app) Catalog background reads never open Login Required by @teemow — After the portal sign-in expired, pages such as the catalog and Settings no longer open the
Login Required dialog by themselves from background reads. It opens only when you do something, like a click or a key press. - (app) Treat notification paths starting // or /\ as external by @teemow — A notification link whose path starts with
// or /\ no longer sends you to another website from the notification bell; it stays on the portal. - (ui-react) Render Mermaid blocks in markdown as diagrams by @teemow — Mermaid code blocks in markdown, such as in Hive’s Knowledge documents, plans, pull request descriptions and READMEs, show as diagrams instead of their source. An invalid diagram shows its source with Mermaid’s error.
Development and CI/CD
Full Changelog: https://github.com/giantswarm/backstage/compare/v3.9.0...v3.9.1
Fixed
- A call to a backend that is reconnecting is no longer answered
server not found. Three failed health probes move a server to Failed with a reconnect due, and the aggregator removed its registry entry until the reconnect registered it again; a call in that window, typically while the backend’s only pod is replaced, was told server not found: <server> as if the server had never existed. The aggregator now remembers a server whose entry it removed while its service is still alive: a call waits up to 10 seconds (or its own deadline) for the reconnect and is dispatched to the reconnected backend, or is answered server <server> is reconnecting: … retry the call shortly. A stopped or deleted server is still server not found. (#1531)
Changed
- (deps) Envoy v1.40.0, livenessprobe v2.20.0 for the CSI companion in #1071 by @teemow
Full Changelog: https://github.com/giantswarm/agent-platform/compare/v4.141.0...v4.141.1
Added
- (agent-platform) Cut long user messages on the session page behind Show more by @marians — On a session’s page, a long message you sent, such as the conversation carried into a continued session or a pasted log, shows its first 10 lines with
Show more instead of filling the page. - (agent-platform, muster, analytics-react) Report tool runs and agent, model and connector lifecycle as usage data by @marians — For operators: the usage data now counts tool runs, deleting agents, creating, editing and deleting models, editing, turning on or off and removing connectors, and sending, answering, stopping, renaming and deleting in sessions. No names, identifiers or typed text are sent.
- (app, analytics-react) Show the upstream notifications in the Notification inbox by @marians — The Agent Platform’s notification bell also lists the notifications other portal features send you, next to your sessions, and marks them read when you open them or choose
Mark all read. - (app, muster) Move the MCP sign-in card into the Notification inbox by @marians — MCP servers that need your sign-in show as one row in the Agent Platform’s notification bell, e.g.
2 MCP servers need your sign-in, with a sign-in button, instead of a card in the corner of every page.
Fixed
Development and CI/CD
Full Changelog: https://github.com/giantswarm/backstage/compare/v3.8.0...v3.9.0
Fixed
muster auth login reports why it cannot reach the server instead of a missing challenge. Against a server whose TLS certificate the host does not trust, or one that refuses the connection, the sign-in failed with no auth challenge available, hiding the x509 or connection error. The discovery probe now keeps the error of a request that got no response, and the login and --force re-login report it (cannot reach <endpoint>: … x509: certificate signed by unknown authority). A server that answers without a challenge still reports no auth challenge available. (#1527)
