orkiva Open this resource#
Console route: /services. This is a namespaced resource; choose the namespace before making a change.
- Select the correct cluster in the sidebar.
- Open Services 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#
Service type, ports and target ports, selectors and related objects.
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 Overview and YAML to compare the declared ports with the target container. Use Related to inspect matching objects and Events/History to diagnose recent changes. Use the common editor for a permitted change, then verify the backend endpoints.
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#
For a service with no reachable backend, compare selectors with pod labels and inspect endpoint resources. A Service object existing does not prove that an ingress, load balancer or application process is serving traffic.
- 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.