The Web Console also provides users with a detailed view into "All Kubernetes Resources" operational on a given Kubernetes cluster.
Users may wish to sort and view the data based on criteria that makes most sense for them. The Console provides a number of filters to make this easy for them.
- View By Cluster
- View by Namespace
- View by Workloads
- View by Helm Releases
- View by Addons
Managed vs Unmanaged Namespaces¶
Managed namespaces are created and managed by the Controller on clusters. The Controller is responsible for the lifecycle of these namespaces. In contrast, unmanaged namespaces are created and managed by users out of band of the Controller. The Controller is not responsible for the lifecycle of these namespaces.
View by Workload¶
Aimed at users that leverage workload configuration and deployments. The biggest benefit to users is that all Kubernetes resources associated with the workload are automatically filtered and presented. This means users no longer have to guess what resources are part of their application.
View by Helm Releases¶
The biggest benefit to users is that all helm deployments to the cluster either using workload configuration or using helm client are automatically displayed.
A number of attributes are tracked for every Kubernetes resource type. Users that wish to view the attributes that are outside the "default" set of filters can use the Column Selector to select their preferred set of attributes
The list of active namespaces on the cluster and the state of health of resources in it.
- Green indicates that all resources in the namespace are healthy
- Red indicates that some/all resources in the namespace are unhealthy
- Replica Sets
- Stateful Sets
- Daemon Sets
Config and Storage¶
The "total count" for every type of Kubernetes resource is displayed on the dashboard. In addition, for Kubernetes resources that can have "state", the data is presented organized by "state" i.e. Healthy or Unhealthy.
In the example above, across all namespaces on this cluster, there are
- 46 Services in total
- 45 Pods in Healthy state and 10 Pods in Unhealthy state.
Users can filter and view the list of Kubernetes resources either by
- Namespaces or
- Helm Releases
The view by namespace is the default filter.
Developers are provided with the facility to quickly investigate and debug issues associated with their running Pods and Containers.
Developers are provided the facility to quickly view the "events" associated with their Pod.
For a pod, click on "Events" under actions
This action performs a "live retrieval" of pre-filtered list of events associated with this pod.
Administrators are provided with a number of contextual actions that they can perform on pods right on the integrated k8s resources dashboard.
Administrator are provided the facility to retrieve and view the logs associated with a specific container in a single click. This enables them to investigate issues quickly and efficiently.
For a pod, click on "Logs" under Actions. This will open a real time, zero trust kubernetes access (ztka) shell to the running container and present the administrator with the Logs.
Exec to Container¶
There are scenarios where the administrator may need to "exec" to a specific container so that they can investigate issues faster.
For a pod, click on "Exec" under Actions. This will open a real time, zero trust kubernetes access (ztka) shell to the running container.
For scenarios where the developer may need to "view" the k8s yaml for a pod to investigate issues
For a pod, click on "Describe" under Actions. This will retrieve the k8s yaml describing the pod operational on the remote cluster.
Useful for scenarios where the developer may need to "delete" a pod on a remote cluster
For a pod, click on "Delete" under Actions.