orkiva Open this resource#
Console route: /clusterroles. This is a cluster-scoped resource; no namespace is part of its identity.
- Select the correct cluster in the sidebar.
- Open ClusterRoles 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#
Rules for API groups, resources, verbs and any aggregation configuration.
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#
Open ClusterRoles and inspect the full rules. Find relevant bindings before broadening a role; a change can affect multiple subjects.
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.
A practical investigation#
A ClusterRole is a rule definition. The binding determines how it is granted. Avoid interpreting its name as proof of its effective permissions.
- 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.