The platform provides a WebSocket endpoint for receiving real-time cluster state change notifications.Documentation Index
Fetch the complete documentation index at: https://dorguai.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Connecting
Message format
All messages are JSON-encoded:| Field | Type | Description |
|---|---|---|
type | string | Event type identifier |
data | object | Event payload |
data.name | string | Name of the affected cluster |
Event types
| Type | Trigger | Description |
|---|---|---|
cluster.added | ClusterPersona created | A new cluster has been discovered |
cluster.updated | ClusterPersona modified | Cluster state has changed (nodes, phase, addons, etc.) |
cluster.deleted | ClusterPersona removed | A cluster has been removed |
Connection lifecycle
Timeouts
| Parameter | Value |
|---|---|
| Write deadline | 10 seconds |
| Pong wait | 60 seconds |
| Ping period | 54 seconds |
| Max message size | 512 bytes (incoming) |
The WebSocket is notification-only — messages flow from server to client. The server does not process incoming messages from clients beyond ping/pong frames. To query cluster data, use the REST API.
Reconnection
The platform frontend automatically reconnects after 5 seconds if the WebSocket connection drops. When building your own client, implement similar reconnection logic:Extracting data
WebSocket events carry only the cluster name, not the full cluster object. After receiving an event, fetch the updated data from the REST API:REST API
HTTP API for fetching cluster data
Real-time updates
How the frontend uses WebSocket events