Reference
Components
Every class in the library, rendered in both themes.
Buttons
ok
warn
danger
info
pending
idle
sha256:9f2ae41c
region: jkt-01
state: running
production
⌘K
UMRAKD+7
Banners and toasts
Running
28/32
Memory
92%
Spend
$12,480
Loading
Area and bars
ingress
egress
Donut, gauge, meters
68%
healthy
healthy
node-jkt-01
node-jkt-02
node-jkt-03
Table variants
striped · bordered · compact| Name | State | Shape | Node | Age |
|---|---|---|---|---|
| web-01 | running | c2.4x | node-jkt-01 | 14d |
| db-02 | provisioning | m4.2x | node-jkt-01 | 2m |
| cache-01 | failed | b1.1x | node-jkt-03 | 6h |
| queue-03 | draining | c2.2x | node-jkt-02 | 31d |
Page 2 of 9
Lists and media
registry.marspanel.dev/api
12 tags · 4.2 GiB
signed
ci-deploy-key
No expiry set
RA
Rania
Owner · last seen 4m ago
cluster-backup-2026-09-14.tar.zst1.8 GiB
KD
Kadek09:41
Readiness probe timeout is 1s but the app takes 1.4s to warm. That is the whole bug.
Disclosure and steps
Image
2Shape
3Network
Why did this instance restart?
The liveness probe failed three consecutive times. Liveness restarts the container; readiness would only have pulled it from rotation.
Is a snapshot a backup?
No. A snapshot is copy-on-write on the same node and dies with it. A backup lives in object storage and survives node loss.
What counts as N+1?
Every workload still fits after losing any single node. At 92% memory quota this cluster no longer does.
- Instance ID
- i-9f2ae41c7b03d8
- Image digest
- sha256:9f2ae41c7b03d8
- Private address
- 10.20.4.17/22
- Created
- 2026-08-31 09:14 UTC
09:12:01INFOlistening on 0.0.0.0:8080
09:12:44WARNreadiness probe exceeded 1s budget (1.41s)
09:13:02ERRORremoved from load balancer rotation
09:02 — scheduled onto node-jkt-02
09:04 — pulling image
09:12 — readiness degraded
09:13 — removed from rotation
Forms
Lowercase letters, digits and hyphens.
Underscores and capitals are not valid in a hostname.
https://
.marspanel.dev
42 / 240
Labels
Placement
Cloud-init
Verification code
Estimated $74.20/month
Terminal and diff
$ marspanel instance list --state failed
NAME NODE AGE REASON
cache-01 node-jkt-03 6h ImagePullBackOff
$
readinessProbe: httpGet: { path: /healthz, port: 8080 } timeoutSeconds: 1 # too tight
14 timeoutSeconds: 1
15- failureThreshold: 1
15+ failureThreshold: 3
Topology
lb-public-01203.0.113.10
web-01in rotation
api-04removed · readiness
Board
Triage3
cache-01 image pull backoff
Bucket quota alert is noisy
In progress2
Raise readiness failureThreshold
Done7
Add N+1 capacity check
September 2026
Mon
Tue
Wed
Thu
Fri
Sat
Sun
31
1
2Patch window
3
4Backup verified
5
6
7
8Cert expires
9
10
11Migration+2 more
12
13
14cache-01 down
15
16
17
18
19
20
KD
Kadek
That is the whole bug.
RA
Rania
Quota bumped, try again.
#
#incidents
cache-01 is still failing.
KDKadektyping
Today
KD
Readiness timeout is 1s but warmup takes 1.4s.
09:41
So it never passes. Raising failureThreshold to 3.
09:43
KD
That is the whole bug.
09:44
No snapshots yet
Snapshots are copy-on-write and live on the same node.
No matches
Nothing matched state=failed in this region.
Not permitted
Your role viewer cannot delete instances.
Control plane unreachable
Last successful poll 4 minutes ago.
Upload an image
Raw, qcow2 and OCI archives are accepted.
Restore complete
All 14 volumes verified against their checksums.