Containers
Inspect app pods, container readiness and restarts.
Kubarr-managed apps run as Kubernetes workloads, commonly in app-specific namespaces. Inspect pod state, container readiness and restart counts to see whether a workload is running and where it may be failing. Containers in one pod share that pod’s network; namespaces are organizational boundaries, not virtual machines or a complete security boundary.
How it works
Kubernetes schedules chart-defined pods and containers onto cluster nodes. The dashboard reports their observed phase, readiness and restart information from Kubernetes, helping you locate a failing pod or container. Containers in the same pod share its network namespace and can communicate over localhost; a namespace boundary by itself does not isolate network traffic.
These views show or configure aspects of your Kubernetes cluster. Availability and behavior depend on your deployed components, cluster configuration and supported app charts.
Check the result: Use Kubernetes workload status and the relevant chart documentation to verify behavior. Observability views show reported state and do not themselves enforce network or storage boundaries.