gke

Signed-off-by: leecalcote <[email protected]>

catalog/0aa86dd0-415c-4bf8-ae76-832560470b74/artifacthub-pkg.yml

@@ -5,7 +5,12 @@ name: run-daemonset-on-gke-autopilot
 category: networking
 displayName: Run DaemonSet on GKE Autopilot
 createdAt: "2024-04-18T04:08:37Z"
-description: This design maps to the "Exploring Kubernetes Pods with Meshery" tutorial and is the end result of the design. It can be used to quickly deploy an NGINX pod exposed through a service.
+description: |
+  GKE uses the total size of your deployed workloads to determine the size of the nodes that Autopilot provisions for the cluster. If you add or resize a DaemonSet after Autopilot provisions a node, GKE won't resize existing nodes to accommodate the new total workload size. DaemonSets with resource requests larger than the allocatable capacity of existing nodes, after accounting for system pods, also won't get scheduled on those nodes.
+
+  Starting in GKE version 1.27.6-gke.1248000 clusters in Autopilot mode detect nodes that can't fit all DaemonSets, and over time, migrate workloads to larger nodes that can fit all DaemonSets. This process takes some time, especially if the nodes run system Pods, which need extra time to gracefully terminate so that there's no disruption to core cluster capabilities.
+  
+  In GKE version 1.27.5-gke.200 or earlier, we recommend cordoning and draining nodes that can't accommodate DaemonSet Pods.
 logoPath: ../../assets/images/brand/meshery-logo.svg
 logoURL: https://raw.githubusercontent.com/meshery/meshery.io/0b8585231c6e2b3251d38f749259360491c9ee6b/assets/images/brand/meshery-logo.svg
 # digest: String that uniquely identifies this package version (optional)