orkiva Open this resource#
Console route: /crds. This is a cluster-scoped resource; no namespace is part of its identity.
- Select the correct cluster in the sidebar.
- Open CRDs 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.
What to inspect#
CRD name, group, versions, scope and schema in the definition.
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 CRDs and select the definition’s instance-list route. Choose a namespace for namespaced instances; cluster-scoped instances use their own scope. Open an instance to inspect its spec/status and use authorized generic actions.
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#
An installed CRD describes an API but does not prove its controller is running. Use the CRD’s served version/schema and the actual instance status. Creating arbitrary YAML that violates the schema will be rejected.
- 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.