Availability and navigation#

Console route: /podmetrics. This entry is optional in the resource catalog and may be hidden from the sidebar until an administrator enables it in General settings. The cluster must also serve a supported API version. Enabling the link does not install that API or its controller.

Scope: namespaced; select the relevant namespace or All Namespaces.

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.

Inspect an object#

  1. Select the intended cluster, then open the resource route or its enabled sidebar link.
  2. Use the available list search and namespace controls to locate the object.
  3. Open the detail page and inspect Overview, Describe and the full YAML document as available.
  4. Review timestamp/window and container resource usage.
  5. Refresh and compare the observation with the related workload or controller.

Use this information#

Use this as a current metrics observation. The metrics API is read-oriented; do not attempt to create or edit usage values. Historical charts use a separate metrics integration.

Editing and lifecycle#

Use the resource list and detail page to inspect this resource. Where the API and your permissions allow mutations, use the shared create, YAML, clone and delete controls described in resource actions. Read-only APIs and controller-owned observations must not be treated as editable application configuration.

Before a permitted change, identify the object’s owner and consumers, review the entire proposed document and preserve the source configuration. After saving, inspect the resulting status and related objects; admission and reconciliation can report errors after a syntactically valid submission.

If the page is unavailable#

Check optional navigation visibility, Orkiva role scope, Kubernetes connection permissions and the cluster’s served API versions in that order. The versioned handler discovers a supported API before dispatching requests. An unavailable API is different from an empty list, and an empty list is different from a permission denial.