Catalog Details
CATEGORY
deploymentCREATED BY
UPDATED AT
June 05, 2024VERSION
1.0
What this pattern does:
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.
Caveats and Consideration:
For all GKE versions, we recommend the following best practices when deploying DaemonSets on Autopilot: Deploy DaemonSets before any other workloads. Set a higher PriorityClass on DaemonSets than regular Pods. The higher PriorityClass lets GKE evict lower-priority Pods to accommodate DaemonSet pods if the node can accommodate those pods. This helps to ensure that the DaemonSet is present on each node without triggering node recreation.
Compatibility:
Recent Discussions with "meshery" Tag
- Jun 04 | How to setup Meshery Operator for local machine
- Jun 04 | Error on terminal when I ran `mesheryctl system start`
- Jun 04 | No connection shown in Docker Desktop Meshery extension
- Jun 04 | Showing no connections in meshery playground as well as in Docker meshery extension
- Jun 03 | Error in Meshery Server logs
- Jun 03 | Looking for Meshmate for first PR
- Jun 02 | Bug in MesheryPlayground production website in Deploying and Removing Adapters
- Jun 01 | Error encountered when trying to refresh after deploying adapter in settings in meshery playground
- Apr 14 | Unable to deploy meshery to minikube
- May 30 | Looking for a meshmate to help with first PR