diff --git a/runbooks/source/monitor-eks-cluster.html.md.erb b/runbooks/source/monitor-eks-cluster.html.md.erb index a651a5c8..c547374a 100644 --- a/runbooks/source/monitor-eks-cluster.html.md.erb +++ b/runbooks/source/monitor-eks-cluster.html.md.erb @@ -26,16 +26,15 @@ Press `:` to activate the command mode and type `nodes` and press Enter. Here, you can see a list of your cluster's nodes along with their status, CPU, memory usage, version, Pods and age. ####Sorting for nodes -K9s allows you to sort resources based on different metrics, providing flexibility in how you view your cluster's data. +K9s allows you to sort resources based on different metrics, providing flexibility in how you view your cluster's data. This can be particularly useful in troubleshooting or Cluster Upgrade when you need to quickly identify which nodes are under the most strain or which are the newest or oldest. - -``` - Sort Age +``` + Sort Age Sort CPU - Sort Memory + Sort Memory Sort Name - Sort Pods + Sort Pods Sort Role ``` @@ -85,7 +84,7 @@ During EKS Cluster upgrade, it is recommended to filter pods by status `Containe ####Sorting for Pods Sorting concecpt for pods is similar to sorting for nodes. You may refer to [Sorting for nodes](#sorting-for-nodes) for more details. -``` +``` Sort Age │ Sort CPU │ Sort CPU/L │ @@ -102,8 +101,6 @@ Sorting concecpt for pods is similar to sorting for nodes. You may refer to [Sor Sort Status │ ``` - - ###Monitoring Events To view and monitor events: @@ -126,20 +123,20 @@ Only events related to the specified namespace will be shown. ####Sorting for Pods Sorting concecpt for pods is similar to sorting for nodes. You may refer to [Sorting for nodes](#sorting-for-nodes) for more details. -``` - Sort Age - Sort Count - Sort FirstSeen - Sort LastSeen - Sort Name - Sort Namespace - Sort Reason - Sort Source +``` + Sort Age + Sort Count + Sort FirstSeen + Sort LastSeen + Sort Name + Sort Namespace + Sort Reason + Sort Source Sort Type │ ``` -During EKS Cluster upgrade, it is recommended to sort events in default view by last seen in ascending order. This sorting method enhances your understanding by providing a chronological sequence of events. -It ensures that you can easily track the progression of the upgrade and promptly identify any recent issues that may arise. +During EKS Cluster upgrade, it is recommended to sort events in default view by last seen in ascending order. This sorting method enhances your understanding by providing a chronological sequence of events. +It ensures that you can easily track the progression of the upgrade and promptly identify any recent issues that may arise. ### Further reading For more details, you may refer to the built-in help by pressing `?` within K9s or below pages. @@ -172,7 +169,7 @@ stern -n It's particularly useful during the update process of EKS add-ons, offering visibility into how changes affect pod operations. ``` -stern --namespace kube-system +stern --namespace kube-system ``` Stern sometimes may reach the maximum number of log request which is 50 by default, and you may use the flag `--max-log-requests ` to increase the log limit, for example @@ -184,4 +181,4 @@ stern -n kube-system kube-proxy --max-log-requests 500 For more details, you may refer to the below pages. - [Stern Doc](https://github.com/stern/stern?tab=readme-ov-file#usage) -- [Tail Kubernetes with Stern](https://kubernetes.io/blog/2016/10/tail-kubernetes-with-stern/) \ No newline at end of file +- [Tail Kubernetes with Stern](https://kubernetes.io/blog/2016/10/tail-kubernetes-with-stern/)