orkiva Open this resource#
Console route: /statefulsets. This is a namespaced resource; choose the namespace before making a change.
- Select the correct cluster in the sidebar.
- Open StatefulSets and narrow the list using the available namespace/search controls.
- Select the exact object by name. Verify its scope and identity at the top of the detail page.
For screenshots of the shared list, detail and creation controls, see the resource actions visual guide. Available actions depend on the resource and your permissions.
What to inspect#
Desired and ready replicas, pod identities, containers, volume information and events.
Refresh the resource when you need the latest observation. Overview fields summarize the object; YAML exposes the complete returned document. A placeholder or missing status field should not be read as a successful or zero-valued result.
Use the available features#
Use Scale for a deliberate replica change and Restart for the workload restart flow. Containers provides the available container editor. Review Volumes before changing a workload that depends on persistent claims. Logs and Terminal select an actual pod/container; History and Events provide the change context.
Describe, Clone, YAML editing and Delete are shared resource actions where the page and your permissions allow them. Read Create, edit, clone and delete resources before applying a change.
For field-by-field instructions, see Edit images, resources and environment.
A practical investigation#
When a replica is stuck, inspect its pod, associated PVC and events. A successful scale request does not prove that the new replica has attached storage or joined the application. Do not assume deleting the StatefulSet is an application-data rollback.
- Establish the current state and the symptom you want to resolve.
- Identify whether a controller, Helm release or Delivery project owns the object.
- Make the smallest authorized change through that owner when possible.
- Refresh and verify the resulting resource state. Inspect related objects rather than stopping at a successful save message.