Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

Cluster Scaled Success Block for React

A confirmation window for a scaled cluster: twelve node slots in a framed canvas that a number field redraws, an Autoscale switch that dashes the room to grow, and the vCPU, memory, requests and monthly cost worked out from typed per-node figures.

Framework
UI library

Preview

Preview width

Installation

Part of Pro
Pro unlocks the code and one-line install of every Pro button and text effect, plus the MCP for your AI editor.
Have Pro already? Sign in to open it.Opens here as soon as you're Pro.

Overview

Show what a new node count buys with this confirmation window for React with Base UI. It is the Hivecrate console, managed Kubernetes, just after a cluster was scaled, in a fixed-height window with no title bar: a top bar with a success mark, the heading and the one action, the Shine Button that opens the metrics. The page side is a canvas of twelve node slots in a framed box (the nodes the cluster had solid, the nodes added outlined, the rest dashed) with a control bar docked under it: a Number Input for the node count, 3 to 12, and a Switch for Autoscale that dashes the slots the cluster could grow into. Changing the count redraws the canvas and works out the vCPU, memory, requests per second and monthly cost. For managed clusters, node pools and any capacity you can resize.

FAQ

What stays in the page, and how do I wire it for real?

Nothing was scaled and nothing is billed. The node figures (4 vCPU, 16 GB, 1,200 requests a second and 160 dollars a month per node) are typed sample data, and the count only redraws the window. To wire it, set PER_NODE from your node pool, EXISTING from the size before the change and MIN and MAX from your limits; every figure and the sentence in the foot are worked out from them, and the cost uses whole cents.

How does the node field behave?

It takes a whole number from 3 to 12 with plus and minus steppers. The canvas follows each valid number as it is typed, a number outside the range is cut to it when the field loses focus (40 becomes 12, 1 becomes 3), and an empty field goes back to the count shown.

What does Autoscale do?

It is a switch, off on load. Turned on, the slots beyond the count are drawn dashed and hatched as room to grow, and the sentence adds how many more nodes the cluster could take and the most that would cost a month; at 12 nodes it says there is no room left. Nothing is enabled: it only changes what the window shows.

Is the canvas accessible?

Each slot has its number and, for assistive technology, what it is (existing node, added node, room for autoscale or free slot), the key under the canvas names the three looks, and the sentence in the foot, which is the window's one live region, says what the count gives each time it changes. The canvas always has twelve slots, so it never changes height.

How does the window behave on a phone?

It keeps its height (36rem on a phone, 46rem from the medium breakpoint) and scrolls inside itself. Below the large breakpoint the control bar moves above the canvas so the number field is on the first screen, and the three figures stay in a row under the canvas.

  • Pro

    A confirmation window for a new load balancer: the routing drawn top-down from clients through the balancer to three zones of backend dots, the entry hostname with a copy button, and a zone picker that lists the chosen zone's four backends with their addresses.

  • Pro

    Deployment Live Success

    Builds and deploys

    A confirmation window for a live deploy: a drawn browser with the real address and a copy button, a group of buttons that redraws the site at desktop, tablet and phone width, and the deploy's facts and four passed checks beside it.

  • Pro

    Instance Provisioned Success

    Servers and storage

    A confirmation window for a new server: a list of its facts beside three connect tabs (SSH, SFTP and Docker context) with copyable commands, and the 48 seconds it took as four steps on a time axis.

  • Pro

    System Rebooted Success

    Servers and storage

    A confirmation window for a rebooted host: a table of four hosts with the rebooted one chosen, and a detail panel with its uptime, load, last boot and services in start order, each with the second it was healthy.

  • Pro

    A confirmation panel for a raised API limit: a group of buttons for all regions, EU and US, one derived sentence with a before-and-now meter, three endpoints with the same paired bars and their limits in words, the burst bucket, and a local benchmark.

  • Pro

    A confirmation panel for a raised storage limit: a capacity ruler from 0 to 2 TB with the space used, the old limit and the space added, three figures worked out from the same numbers and a forecast of when the free space runs out at a growth rate you pick.