Skip to content

Clusters pages: Edit, Providers and runtime slice through cluster-manager #2247

Description

@teemow

Problem

On an installation that carries the KaaS product (giantswarm/giantswarm#37611), a person cannot change a cluster from the Clusters pages: no release upgrade, no edit of the cluster's own node pools. Nothing shows which providers the installation offers or whether they are ready. A stuck creation sends the person to a shell. Create and Delete are #2624.

Proposed solution

Where cluster-manager is present on an installation (feature-detected by the x_cluster-manager_* tools the installation's muster lists, get_info for the modes), every action calls cluster-manager's MCP tools through muster as the signed-in user. There is no REST client, proxy route or scaffolder template. Each review step shows the tool's dry run and offers Deploy (mode: apply) and Commit (mode: commit, the pull request as the person).

  • Cluster detail: Edit on the Release and Node pools tabs, through update_cluster (release upgrade, the cluster's own node pools).
  • Stuck creation: the CAPI conditions and the failing HelmRelease.
  • Installation page: Providers, the installed providers with their readiness and Install provider through install_provider.
  • CPU clusters: the runtime slice's readiness, and the cluster's agents as a dimension of the agent pages.

Acceptance criteria

  • Edit upgrades a release and changes a node pool, with Deploy and Commit, from the dry run.
  • The Providers section shows readiness per provider and installs one.
  • A stuck creation shows its conditions and the failing HelmRelease.
  • Tests for the new actions and section; loading, empty, error and success states follow the gs-uidev rules.

Blocked by

  • cluster-manager's update_cluster and install_provider (giantswarm/giantswarm#37611).

Activity

  1. changed the title [-]Clusters pages on installations with the KaaS product: Create opens the create-cluster template, Node pools/Release edit actions open the edit template pre-filled, Delete behind a name-typing confirm, Providers section with readiness and Install provider[/-] [+]Clusters pages call cluster-manager as the user: Create / Edit (release, node pools incl. GPU) / Delete dialogs through the agent-platform-backend proxy with the user's Dex ID token; Providers section with readiness and Install provider; the cluster's agents as a dimension of the agent pages; runtime-slice readiness[/+] on Sep 5, 2026
  2. changed the title [-]Clusters pages call cluster-manager as the user: Create / Edit (release, node pools incl. GPU) / Delete dialogs through the agent-platform-backend proxy with the user's Dex ID token; Providers section with readiness and Install provider; the cluster's agents as a dimension of the agent pages; runtime-slice readiness[/-] [+]Clusters pages call cluster-manager as the user: Create / Edit (release, node pools incl. GPU) / Delete dialogs through cluster-manager's MCP tools via muster, review step with Deploy (apply) and Commit (PR as the person) — no agent-platform-backend proxy route; Providers section with readiness and Install provider; the cluster's agents as a dimension of the agent pages; runtime-slice readiness[/+] on Sep 6, 2026
  3. changed the title [-]Clusters pages call cluster-manager as the user: Create / Edit (release, node pools incl. GPU) / Delete dialogs through cluster-manager's MCP tools via muster, review step with Deploy (apply) and Commit (PR as the person) — no agent-platform-backend proxy route; Providers section with readiness and Install provider; the cluster's agents as a dimension of the agent pages; runtime-slice readiness[/-] [+]Clusters pages: Edit, Providers and runtime slice through cluster-manager[/+] on Sep 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions