Short-lived token
One-time enrollment.
Kubernetes Operator
Kubernetes connection, secure and revocable
The whycloud Operator installs with Helm, enrolls with a short-lived token and only connects outbound.
- Operator
- outbound connection
- Multi-cluster
- one console
- RBAC
- organization roles
ClustersLIVE
| Cluster | Nodes | Status |
|---|---|---|
| prod-tehran | 12 | Healthy |
| stage-tehran | 4 | Healthy |
| edge-tabriz | 3 | Warning |
Live
HOW IT WORKS
How it works
- 1
Install the operator
Install the lightweight whycloud operator with Helm.
- 2
Confirm the connection
The cluster appears in the console with its own identity.
- 3
See resources
Nodes, workloads and events in one place.
- 4
Controlled operations
Deploy and roll back with audit and roles.
Capabilities
Kubernetes Operator
Helm chart
Standard installation.
Outbound WebSocket
No inbound ports.
USE CASES
Use cases
Clusters across sites
One view for production, staging and edge clusters.
Development teams
Scoped namespace access without a shared kubeconfig.
Compliance and audit
Every change recorded for review.
Technical specs
- Kubernetes
- 1.27+
- Install
- Helm chart
- Transport
- Outbound, mTLS
- Status
- Beta
FAQ
Frequently asked questions
What access does the Operator have?
Access limited to the defined RBAC.
Are managed cloud clusters supported?
Yes; any conformant cluster that can run the operator can connect.
Turn on your own cloud today
Create an account and connect your first server in under five minutes.