An overview of your clusters is preeminent to the management of them. Container Cluster Management provides such an overview in the form of the Cluster page. From there you can detect potential trouble spots that can guide you to other more specific support elements such as Network and Workloads.
Cluster details navigation menu
When you navigate to the Cluster details page, the service defaults to the Cluster Overview page. The following selections are available in the left navigation bar, providing details for specific elements supporting your container clusters:
Overview
Namespaces
Nodes
Events
Alerts
Overview
The Cluster overview page presents a detailed overview of a cluster. It displays the following information:
Connection:
Provider that hosts the cluster connection.
Provider:
Displays the name of the Provider.
Location:
Displays the code of the location where the cluster is located.
Application:
Displays all applications associated with the current cluster.
Environment:
The name of the environement in which the cluster resides.
Version:
The Kubernetes version of that cluster.
Deprecated APIs:
The list of APIs that have been deprecated for the current cluster.
Created Date:
The date on which the cluster was created.
Last Sync:
The length of time since the container was last synchronized.
Pods:
The number of pods running in the cluster. you can select this option to go to the Pods to view all the required information about the pods configured in the cluster.
Nodes:
The number of nodes running in the cluster. you can select this option to go to the Nodes to view all the required information about the nodes configured in the cluster.
Events:
The number of events that have occurred in a cluster. you can review all the required information about all the events happening in the cluster by going to the Events and selecting this option.
Alerts:
The total number of alerts for the current cluster.
Actionable Insights:
All supported actionable insights for the current cluster.
CPU Resources:
This graph represents the CPU Resource usage by the cluster over a period of time. The red line indicates the
CPU limit
. The green line indicates the
CPU usage
, and the yellow line indicates the
CPU requests
. This graph lets you quickly identify whether CPU resource usage exceeds the specified limit. On hovering over any particular line on the chart, the tooltip displays the CPU limit, CPU usage, and CPU requests at that specific time.
Memory Resources:
This graph represents the memory resources used by the cluster over a period of time. The red line indicates the
Memory limit
. The green line indicates the
Memory usage
, and the yellow line indicates the
Memory requests
. This graph lets you quickly identify if the Memory resource usage is above the specified limit. On hovering over any particular line on the chart, the tooltip displays the memory limit, usage, and requests at that specific time.
Pods:
This graph represents the number of running and pending pods in the cluster across a period of time.
The duration for the CPU and memory resources graphs is set to
5 minutes
by default. This can be changed by using the Drop-down menu present above the charts.
Namespaces
This section gives you a detailed view of all the cluster's namespaces. We fetch this information from your cluster using on-demand discovery that taps into Kubernetes' APIs.
Check out these key details in the Namespace section:
Name
: Here, you see each namespace's name.
Pods
: This count reflects the pods in each namespace. Click on the number to delve into pod details.
CPU Requests
: Find out how much CPU power each namespace requests.
CPU Limits
: This shows the maximum CPU resources each namespace can use.
Memory Requests
: Discover the memory demands of each namespace.
Memory Limits
: Understand the upper limits of memory set for each namespace.
Keep in mind you need Prometheus activated on your cluster to view the statistics data – including CPU, memory requests and limits, and pod count.
To view more details about a namespace, you can either click on the row or the
View details
option present at the end of the row. The details about the namespace are presented in a side panel, as shown below.
Nodes
This section presents an overview of the nodes present in a cluster. The data presented in this section is fetched directly from the cluster via on-demand discovery (which uses APIs exposed by Kubernetes).
The following details are presented in this section:
Name:
This column presents the name of the nodes.
OS:
This is the Operating System reported by the node.
CPU Requests:
This is the CPU resource request made by the node.
CPU Limits:
This is the specified CPU limit of the node.
CPU Allocation:
This is the allocatable CPU resource for the node.
Memory Request:
This is the request for memory resources made by the node.
Memory Limit:
This is the specified memory limit of the node.
Memory Allocation:
This is the allocatable memory resource for the node.
For each node, further details can be obtained by clicking either on the row directly or on the
View details
option present at the end of each row. The service presents details about the selected node in four tabs:
Conditions:
This tab displays the
Conditions
table with the following columns: Type, Status, Message, Last transition time, and Last Heartbeat time.
Pods:
Presents details about the pods running on the node:
Pods name
Namespace
Container
CPU requests
CPU limits
Memory requests
Memory limits
Pod IP
Click the expand chevron for any pod to view the log for that pod.
Raw JSON:
Presents the JSON script that defines the selected node.
Monitoring:
Presents four graphs:
CPU resources
, displaying usage, requests and limits over time at one-minute intervals:
CPU usage
CPU requests
CPU limit
Physical limit
Memory resources
, displaying usage, requests and limits over time at one-minute intervals:
Memory usage
Memory limit
Memory requests
Physical limits
Network transmitted
, displaying data in Bytes over time at one-minute intervals:
Network transmitted
Network received
File usage
, displaying data in GB over time at one-minute intervals:
Hover over each graph to display data point details.
Events
This section gives details about all the events that have occurred in the cluster. The data displayed here is fetched directly from the cluster via on-demand discovery (which uses APIs exposed by Kubernetes).
The following details are presented in this section:
Type:
This column displays the type of events that have occurred.
Reason:
This column displays the reason for the occurrence of the events.
Namespace:
This column presents the event's namespace.
Message:
This column presents the message related to the event, which is a brief description of what the event is.
Involved Object:
This column displays the object involved with the event.
Count:
This column displays the recorded number of occurrences of the event.
First Seen:
This column displays the date on which the event first occurred.
Last Seen:
This column displays the date on which the event last occurred.
The events can be filtered according to the namespace to which they belong by using the namespace filter Drop-down menu in the top right corner above the events table. By default, events from all namespaces are displayed in the events section.
More details about an event can be found by selecting the
View details
option at the end of each row.
The data here is JSON data for the selected event.
Alerts
This page gives you a complete overview of all the alerts that you has to review for a cluster.
The cluster alerts are presented in three different sections:
Pod Alerts
,
Node Alerts
, and
Cluster Alerts
.
The following details are presented in the Alerts table:
Namespace:
This column displays the namespace to which the Pod or Node where the alert occurred belongs.
Severity:
This column indicates how severe an alert is.
Status:
This represents the status of the cluster.
Pod:
This column displays the Pod where the alert occurred.
Summary:
This presents the overview of the alert.
Description:
This column presents the Description of the alert.
Alert Started At:
This displays the time the event leading to the alert occurred.
You can sort the alerts table according to the status, Severity of the alerts, or the time they occurred to review the alerts according to priority.