How the docs are organized
The documentation set is split into three layers.
Concepts
Terminology for pods, controllers, nodes, namespaces, services, access roles and image metadata.
Operator guide
Practical steps for inspecting objects, reading health, interpreting warning events and moving between related objects.
Reference
Field meanings, policy notes, compatibility expectations, retention windows and escalation boundaries.
Concepts and structure
- Concepts overview — pods, controllers, services and namespace boundaries.
- Platform structure — where cluster services, traffic paths and stateful components fit together.
- Security and access — access boundaries, role assignments and secrets handling expectations.
- Glossary — concise definitions for common portal terms.
Operator guides
Operator guide
Entry page for routine object inspection and cross-links to focused workflow pages.
How to inspect a pod
What to check first when a pod is healthy, degraded or repeatedly restarting.
How to read workload readiness
How to judge rollout health, desired versus ready and when to look at owners or events.
How to review node health
How to read conditions, pressure signals, allocatable values and related scheduling clues.
How to interpret warning events
How to separate noisy but harmless warnings from meaningful operational signals.
How to trace related objects
How to move from pod to workload, node, namespace and event context without losing the thread.
How to review image metadata
How to read tags, digests, update windows and consumers in the registry view.
Reference and policy pages
- Data reference — meanings of fields shown in overview, workload, namespace, node, event and registry details.
- Read-only boundaries — what the portal shows and which actions stay on the administration path.
- Environment compatibility — browser and hosting expectations for a clean operator experience.
- Retention and recovery overview — visibility windows and what to re-check after maintenance or redeployments.
- Escalation policy — when to hand issues to platform, networking, registry or security owners.
- Release notes — changes to labels, fields and operator-facing behavior.
WS110 / WS111 / WS112 access behavior
The WS110 / WS111 / WS112 access behavior page explains how to interpret informational refusals, policy-driven closure, related observability signals and escalation paths across /ws110, /ws111 and /ws112.