On this page
Operate from the Cloud workspace
Read health, activity, usage and support context in the browser, then make changes with an explicit and auditable operation.
These steps describe the intended customer path. Use the interface only after personal access and written confirmation of this capability in your pilot scope.
Before you start
Use the authenticated workspace and the resource scope confirmed for your pilot. Monitoring, backups, high availability, recovery targets and response times are shown only when they are qualified for that scope.
1. Start with the overview
Open the workspace overview before changing a resource. Check freshness, active operations, degraded applications, capacity notices and open support items. An empty list means no current item was returned; it does not prove that a system is unlimited or incident-free.
| View | Useful evidence |
|---|---|
| Health | Observed status, last update, reason and affected scope. |
| Activity | Operation ID, actor, requested change, attempts and terminal result. |
| Usage | Confirmed platform and infrastructure items with period and freshness. |
| Support | Redacted context that can be shared without credentials. |
2. Handle an incident from the page
- 01
Open the affected resource
Follow the link from the alert or activity item and confirm that the organization, cluster and application are yours.
- 02
Read the bounded reason
Use the displayed reason, timestamp, revision and next safe action. Do not copy secrets, tokens or complete request bodies into a ticket.
- 03
Escalate with evidence
Send the operation ID and a short impact statement through the agreed support route. The operator can correlate the browser record with managed infrastructure telemetry.
3. Make changes auditable
Use the action available for your role, review the impact, confirm once and follow the resulting operation. The same history should show who requested the change, what was targeted, what was observed and whether recovery was needed.
4. Keep operations and costs aligned
Review usage and the proposal together. Additional nodes, larger machines, storage, backups or network services may change the total and require an explicit quote. Monitoring, backups, HA and recovery claims remain proposal-specific until the corresponding evidence is approved.
Understand pricing & usage → · Plan backups & prove recovery → · Get useful support quickly →
Use this guide within your agreed pilot scope. Kubernetes examples are not evidence of a generally available Cloud capability.