ui(cluster): Add Fleet autoscaling and notifications - #105
Merged
Merged
Conversation
Administrators can compare runtime and routing choices, see why an adapter is unavailable, and select only providers that the server reports as ready.
Deployment owners can set replica bounds, sustained utilization thresholds, cooldowns, and whether permitted Fleet capacity may be used.
Notification settings now link to practical guidance, shared controls use restrained FlatRun corners, and development builds expose safe previews for Fleet, notifications, and autoscaling.
Fleet and Notifications now have first-class navigation and focused pages. Notification controls use a compact toolbar, while Fleet setup starts with the server name and agent address already filled in.
Agents, Fleet, and Notifications now share one responsive page header. Notifications moves into the lower administration group, and Agents receives the correct page title and breadcrumb.
Targets can be viewed, renamed, tested, or explicitly reconfigured without revealing stored credentials. Compact incident and rule rows open complete views.
Service pages now share a clear identity, breadcrumb, action area, and mobile layout. The header follows FlatRun's compact radius and token system in both themes.
Service pages now reserve space for dismissible operational context instead of repeating navigation. Account, theme, and sign-out controls are consolidated in the top bar.
Page information and actions now share one adaptive row. Dismissing the information preserves access to actions and collapses the row to button height.
Page context can now match the space and alignment each workflow needs. Persistent action headers omit dismissal, while notification guidance and documentation share a focused right-aligned surface.
Agents now follows the shell spacing instead of adding a second inset. Notification tabs, guidance, and documentation share one responsive toolbar.
Context headers have more breathing room while sitting closer to the content they introduce. Service pages retain a compact application density.
Fleet setup now collects the K3s cluster context before checking and selecting the runtime. Operators can complete the connection without editing the agent configuration by hand.
Deployment autoscaling now guides operators through service portability and storage declarations, shows concrete blockers, and prevents unsafe activation.
Admins can review the safe cutover, activate compatible workloads, and see when a deployment is managed by the cluster provider.
Selecting K3s now selects Traefik automatically, while Swarm and standalone Docker select Nginx. Autoscaling status uses the compact control radius.
The capacity option now states that permitted servers must participate in the same runtime cluster.
Fleet servers now lead directly to their deployment inventory from the Fleet table and sidebar. The focused server view keeps remote actions available without presenting local creation controls.
Deployment overview now keeps health and core details together while autoscaling has its own tab. Service images can be updated through a guarded form without editing the full Compose document.
Overview retains three equal columns and exposes image changes beside each existing service action. Common edits no longer require leaving the service context.
Deployment details keep service editing in Overview. Configuration now opens with Settings, followed by Autoscaling and the advanced file editors.
Deployments now default to the current server and show peer workloads only after explicit sidebar selection. The redundant server banner has been removed.
Development builds now use the same API-backed Fleet, notification, deployment, and autoscaling paths as production. This prevents review fixtures and private preview routes from becoming part of the shipped interface.
![sourceant[bot]](https://avatars.githubusercontent.com/in/1161781?s=60&v=4){kind=small}
Deploying flatrun-ui with
|
| Latest commit: |
fb19ea9
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://504ac38e.flatrun-ui.pages.dev |
| Branch Preview URL: | https://feat-cluster-capacity.flatrun-ui.pages.dev |
The next UI beta now covers Fleet management, managed scaling, and grouped notifications alongside the matching agent release.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Make connected servers operational from one UI, including managed scaling and grouped notifications.
This UI depends on flatrun/agent#214. Peer workloads stay scoped to the selected server. Borrowed capacity requires compatible runtime and permission.