Live Namespace View
pods.kube-system
72 objects indexed
What KUBI Shows
See Your Cluster Not Just YAML
Understand your cluster in one visual context without kubectl overload.
kubectl command overload
# Read-only operator workflow
$ kubectl get pods -A
building visual context...
7+
commands collapsed
1
visual graph
0
mutations allowed
100%
READ-ONLY
Beyond kubectl.
See the structure. Not the output.
Manifest to Graph
Stop Reading. Start Seeing.
Raw YAML mutates in place while operational charts adapt in sync. Same source of truth, visualized live.
01apiVersion: apps/v1
02kind: Deployment
03metadata:
04name: api-deployment
05spec:
06replicas: 3
07selector:
08matchLabels:
09app: api
10template:
11metadata:
12labels:
13app: api
14spec:
15containers:
16- name: api-container
17image: api-image:latest
18ports:
19- containerPort: 8080
20resources:
21requests:
22cpu: 100m
23memory: 128Mi
24limits:
25cpu: 200m
26memory: 256Mi
27serviceAccountName: api-service-account
28volumes:
29- name: api-storage
30persistentVolumeClaim:
31claimName: api-pvc
32status: Bound
Validation Engine
Live checks surface cluster risks by severity, link each finding to the affected object, and suggest concrete next actions.
| Error Type | Description | Object | Severity | Suggested Action |
|---|---|---|---|---|
| Missing Endpoints | Service has no available endpoints. | api-service Service | ERR | Ensure backend pods are Ready and label selectors match. |
| Pods Not Ready | Service targets pods that are not Ready. | api-6f8dbf7d Pod | ERR | Inspect readiness probe and container startup logs. |
| Pending PVC | PVC remains in Pending state and cannot bind. | data-pvc PVC | ERR | Verify StorageClass and available capacity. |
| Ingress without Service | Ingress route references a missing backend service. | web-ingress Ingress | WARN | Attach a valid backend Service to ingress rules. |
| RBAC Wildcards | RoleBinding uses wildcard verb in policy rules. | admin-role RoleBinding | WARN | Replace wildcard verbs with least-privilege verbs. |
Your Cluster, in Motion
Advanced Features & Extensibility
KUBI scales from first cluster to expert workflows with external integrations, generated manifests, storage discovery, and endpoint intelligence.
Selected Capability
MCP Server Integration
Connect external MCP servers to stream health metrics, service latency, and audit snapshots into one KUBI context.
mcp:
endpoint: https://metrics.acme.net
authRef: secret/mcp-token
pollInterval: 15sExternal Storage Telemetry
Live storage health for Vitastor, Ceph, and Longhorn.
sync 05:35:16 PM
Disk Usage (Vitastor)
64% used
Capacity410Gi / 640Gi
Available230Gi
Disk I/O (Vitastor)
Read IOPS Write IOPS Peak 1320 IOPS
Simple Pricing
Access
Secure Authentication and Encryption
HTTPSSession TTLPassword Reset
Cookie Session Authentication
KUBI validates credentials on the server and keeps signed-in users in an HTTP-only session cookie backed by SQLite session records.
- The current session is resolved from the kubi_session cookie on each request.
- Active sessions can be revoked per device or globally from the profile.
HTTP-only cookieSQLite sessions
Password Hashing
Passwords are protected with salted scrypt hashes before they are stored in the local application database.
- Plain-text passwords are never persisted.
- Password verification uses timing-safe comparison on the server.
scryptSalted hashes
Session Lifecycle
Active sessions are stored in SQLite and pruned automatically when they expire.
- Default session TTL is 12 hours, or 30 days when Remember me is enabled.
- Expired sessions and password reset tokens are cleaned up server-side.
SQLite-backed12h / 30d TTL
Account Recovery
Users can recover account access through one-time password reset links and optional email delivery.
- Reset tokens are single-use and expire after 30 minutes.
- If email delivery is not configured, reset links are logged locally for development.
One-time token30 min TTL
Blog View all posts
Latest from KUBI
Kubernetes operations guides, product notes, and architecture decisions behind read-only cluster visibility.
Kubernetes Visibility Without Cluster Risk
How read-only Kubernetes visualization helps operators inspect topology, RBAC, storage, and traffic without giving a dashboard write access.
How the KUBI Agent Connection Model Works
A practical overview of when to use browser-direct kubeconfig import and when to use the KUBI agent for private Kubernetes access.