orkiva Open this resource#
Console route: /jobs. This is a namespaced resource; choose the namespace before making a change.
- Select the correct cluster in the sidebar.
- Open Jobs 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#
Completion and failure status, active/succeeded pods, containers and timestamps.
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 Pods to identify the attempt whose output matters, then open Logs for the correct container. Inspect Events for scheduling failures and Volumes for input/output mounts. The detail page also exposes container, terminal, related, history and monitoring surfaces when available. Edit YAML only within the fields accepted by the cluster.
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#
Distinguish an active job from a completed one and a failed attempt from the entire job outcome. Review the owning CronJob if the job was scheduled. Deleting an old record does not rerun the job or restore its output.
- 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.