The Hava container view for your Kubernetes cluster

The Hava container view gives you an overall diagram of your entire Kubernetes cluster. You can see every workload and pod currently running and the namespace they are in, any services or ingress available to your containers, as well as unused or pending capacity.

Service and Capacity Information

The Container View will generally show one main cluster container around one or more namespace containers. Within the namespace containers it will display any services and ingress rules as a row along the top, followed by any workloads and their pods.

Clicking on a service or ingress resource at the top of the namespace will show it's attributes in the right hand panel and will draw a connection to any linked pods on the diagram.

Clicking on the cluster container on the diagram will display a list of all the workloads contained within the cluster, as well as the nodes the cluster is running on. Hovering over the node name will highlight all the pods currently deployed on that node.

Each of the pods running within the workloads are shown as a hexagonal icon that can be clicked to see the information for the specific pod. Pods are displayed in different styles depending on their current state:

Green pods are running successfully.

Yellow pods are in a pending state, usually starting up or shutting down. You can click the pods for more details.

Red pods are in a failed state, usually because of an issue in initialization. You can click the pod for more details.

Dashed pods are spare capacity in the workload, where the desired count is less than the running count.

View Options

By clicking the dropdown at the top right of the diagram you can see options for how you wish your view displayed. For the Kubernetes container view there is also an option to hide default namespaces that is enabled by default.

Toggling this option will show or hide the default Kubernetes namespaces, such as kube-system. This allows the diagrams to represent only the resources you manage and deploy. This option carries across in exports as well.

Last updated