From bf0b398960314a6edd6454552d438727d066e8c0 Mon Sep 17 00:00:00 2001 From: Aldo Culquicondor Date: Mon, 25 Mar 2024 19:48:38 +0000 Subject: [PATCH] Review comments 2 Change-Id: Id709e00009addbd5168e66c63c6cb473f6811ff6 --- .../tasks/troubleshooting/troubleshooting_pods.md | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/site/content/en/docs/tasks/troubleshooting/troubleshooting_pods.md b/site/content/en/docs/tasks/troubleshooting/troubleshooting_pods.md index e58b7228b6..3dc4f7f8d0 100644 --- a/site/content/en/docs/tasks/troubleshooting/troubleshooting_pods.md +++ b/site/content/en/docs/tasks/troubleshooting/troubleshooting_pods.md @@ -6,11 +6,13 @@ description: > Troubleshooting the status of a Pod or group of Pods --- -This doc is about troubleshooting pending Pods when directly managed by Kueue, in other words, -Pods that are not managed by kubernetes Jobs or supported CRDs. +This doc is about troubleshooting [plain Pods](/docs/tasks/run/plain_pods/) when directly managed by Kueue, +in other words, Pods that are not managed by kubernetes Jobs or supported CRDs. +{{% alert title="Note" color="primary" %}} This doc focuses on the behavior of Kueue when managing Pods that is different from other job integrations. You can read [Troubleshooting Jobs](troubleshooting_jobs) for more general troubleshooting steps. +{{% /alert %}} ## Is my Pod managed directly by Kueue? @@ -58,8 +60,10 @@ Events: Warning ErrWorkloadCompose 14s pod-kueue-controller 'my-pod-group' group has fewer runnable pods than expected ``` -Note that the above event might show up for the first Pod that Kueue observes, and it will remain +{{% alert title="Note" color="primary" %}} +The above event might show up for the first Pod that Kueue observes, and it will remain even if Kueue successfully creates the Workload for the Pod group later. +{{% /alert %}} Once Kueue observes all the Pods for the group, you will see an output similar to the following: @@ -98,8 +102,3 @@ Kueue will remove the finalizer from Pods when: Once a Pod doesn't have any finalizers, Kubernetes will delete the Pods based on: - Whether a user or a controller has issued a Pod deletion. - The [Pod garbage collector](https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#pod-garbage-collection). - -## See Also - -- Read [Troubleshooting Jobs](troubleshooting_jobs) to learn generic troubleshooting steps for jobs - managed by Kueue