diff --git a/6f725e19d60535b3896db2dda83afeaa5405eae6 b/6f725e19d60535b3896db2dda83afeaa5405eae6
index a809478c9..1823b49b9 100644
--- a/6f725e19d60535b3896db2dda83afeaa5405eae6
+++ b/6f725e19d60535b3896db2dda83afeaa5405eae6
@@ -98,6 +98,29 @@
       "revId": "6f725e19d60535b3896db2dda83afeaa5405eae6",
       "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
     },
+    {
+      "unresolved": true,
+      "key": {
+        "uuid": "f64bd2a4_62f9efc7",
+        "filename": "kubernetes/kubernetes-1.24.4/debian/deb_folder/patches/Identify-platform-pods-based-on-pod-or-namespace-labels.patch",
+        "patchSetId": 3
+      },
+      "lineNbr": 98,
+      "author": {
+        "id": 8768
+      },
+      "writtenOn": "2024-04-05T22:51:13Z",
+      "side": 1,
+      "message": "this shouldn\u0027t be hardcoded, there is a default in the Kubelet code but it can be overridden via the --kubeconfig runtime flag\n\n\nAlso, why do we need to make a new k8sclient?  Doesn\u0027t kubelet already talk to the K8s API?   And do we really want to be creating a new connection to the K8s API server every time we try to schedule a pod?",
+      "range": {
+        "startLine": 98,
+        "startChar": 43,
+        "endLine": 98,
+        "endChar": 71
+      },
+      "revId": "6f725e19d60535b3896db2dda83afeaa5405eae6",
+      "serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
+    },
     {
       "unresolved": true,
       "key": {