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. Also, users can view the resource(s) count displayed at the top.
- View By Cluster
- View by Namespace
- View by Workloads
- View by Helm Releases
- View by Addons
Namespaces are created and managed by the Controller on clusters. The Controller is responsible for the lifecycle of these namespaces. Users can view the count of Namespace in the table heading and all the namespaces are listed in the table as shown below.
Kubernetes events are a resource type in Kubernetes that are automatically created when resources have state changes, errors, or other messages that should be broadcast to the system. Events are an invaluable resource when debugging issues in your Kubernetes cluster.
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
Config and Storage¶
- Role Bindings
- Service Accounts
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
- 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.
Administrators are provided with a number of contextual actions that they can perform on pods right on the integrated k8s resources dashboard.
The below table shows the actions availability for each resources:
|Resources||Edit yaml||Describe||Download||Events||Shell and Logs||Delete|
|Roles/ Role Bindings/Service Accounts||YES||YES||YES||N/A||N/A||YES|
Administrators can edit the running resource yaml file using the Edit Yaml option
A yaml config file appears on the right pane. You can update a few parameters that are allowed and click Update. For scenarios where a parameter is not allowed to update, an error message appears as shown in the below example
For scenarios where the developer may need to view the details of a resource to investigate issues. For a resource, click Describe under Actions.
This will show the details describing the resource operational on the remote cluster.
To download the resource yaml file to your system, click Download. On successful download, a success message appears as shown in the below example.
Developers are provided the facility to quickly view the events associated with their Pod. Click Events from the Actions list.
This action performs a live retrieval of pre-filtered list of events associated with this pod.
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 Shell and Logs under Actions and select Logs icon.
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 Shell and Logs under Actions and select Exec icon.
This will open a real time, zero trust kubernetes access (ztka) shell to the running container.
Useful for scenarios where the developer may need to "delete" a pod on a remote cluster
For a pod, click on "Delete" under Actions.