Cluster

an overview of your clusters is preeminent to the management of them 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 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 note 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 note prometheus needs to activated on the 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 file used file capacity 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 have to review for a cluster cluster alerts are categorized into two distinct sections pod alerts and cluster alerts the columns in the corresponding tables differ between these categories for pod alerts, all existing columns are detailed below conversely, cluster alerts do not include the namespace and pod columns within the table 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 the severity of an alert 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 workloads docid\ wvn8xyjcqfqwvmplgzomz acquire essential insights into kubernetes components such as pods, deployments, and others, which are crucial for effective cluster optimization network docid\ ti60tc1asurlbdphuo8hw explore elements of the network component cluster configuration docid\ yhjwgbls4mldauw5 kyg8 learn the configuration procedures that enable secrets and hpa (horizontal pods autoscaler) storage docid\ p9xj ftdl57 sbiydlvds understand the storage architecture cluster access control docid\ gfbrukukslm60qq3cjn8y manage your kubernetes cluster access using a role based approach policy docid\ iio0qx21cmj5fb0sv7d9k manage policies and attributes supported by the service custom resources docid\ rz 1x6by2k9s1e6x86jdd set custom resource definitions to manage objects such as namespaces, pods and services