Skip to content
antalos

Rancher · Use

Rancher provides a browser workspace for inspecting Kubernetes clusters, workloads, namespaces, and access. In antalos it runs inside the cluster it manages. Use it to understand current state and investigate workloads, while keeping long-lived desired configuration in the GitOps repository.

Access and audience

For this installation, use rancher.antblu.net. If you use another antalos installation, open the address supplied by its administrator. Ask for the account or role you need before starting.

Your first workflow

  1. Open Rancher, sign in, and select the intended cluster and project before viewing workloads.

  2. Choose the namespace and inspect the workload’s pods, events, logs, and resource usage. Identify whether the issue is scheduling, startup, readiness, or application behavior.

  3. Use the resource view to understand the Kubernetes objects involved. Record the namespace and object name when escalating an issue.

  4. Make persistent changes in the owning antalos manifest. Argo CD may reconcile a one-off UI change back to the repository value.

Get help

Report the cluster, namespace, and action you could not complete. Do not alter unrelated workloads to work around an access error. Rancher access and the application you are inspecting can fail separately.

During an interruption

The management interface can be unavailable while applications keep running. Ask the administrator to distinguish a Rancher access issue from a workload outage.

Administrators can read the architecture and recovery limits.

Official documentation

Use the official Rancher documentation for the complete feature reference. Some features depend on the installed version and options. If the manual differs from what you see, ask your administrator which version and features are enabled.

For antalos-specific state and availability, continue to Infrastructure Explanation. For installation and integration setup, use Deployment and Admin Guide.