Cluster Autoscaler

Related topics

• Cluster Autoscaler configures node pool From the official documentation: “This document describes the cluster autoscaler, which automatically controls the size of your node pools.”
• Cluster Autoscaler is part of GKE From the official documentation: “For GKE Standard clusters, the cluster autoscaler automatically resizes the number of nodes within a node pool based on workload demands.”
• Cluster Autoscaler configures managed instance group From the official documentation: “If adding a node would let a Pod get scheduled cluster autoscaler adds a new node to the managed instance group (MIG).”
• Compute Engine is an alternative to GKE From the official documentation: “To use TPU7x, you can use Google Kubernetes Engine (GKE) or Compute Engine.”
• node pool is part of GKE From the official documentation: “You create a cluster with [one node pool](/kubernetes-engine/docs/concepts/node-pools) (the default one).”
• GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
• health check configures managed instance group From the official documentation: “Configure auto-healing for the MIG by using the newly created health check.”
• Cloud Load Balancing works with managed instance group From the official documentation: “It configures the load balancer to connect to the instance group.”
• GKE works with health check From the official documentation: “A health check, which provides health checking for the VMs and Google Kubernetes Engine (GKE) Pods in your deployment.”
• managed instance group is part of Compute Engine From the official documentation: “Checks if a Compute Engine Managed Instance Group (MIG) is configured as Zonal.”
• Cloud Load Balancing works with GKE From the official documentation: “GKE and GKE Enterprise network controllers also support the deployment of Cloud Load Balancing for built-in integration with container networking.”
• Cloud Load Balancing works with node pool From the official documentation: “In the following diagram, Cloud Load Balancing distributes traffic to a node pool that spans three zones.”
• Compute Engine works with GKE From the official documentation: “For example, Google Kubernetes Engine (GKE) can cause usage in Compute Engine.”
• GKE works with global external Application Load Balancer From the official documentation: “After you [create the equivalent resources](#migrate-resources), exposing external endpoints behind a global external Application Load Balancer enables you to gradually migrate traffic between Cloud Run and Google Kubernetes Engine (GKE).”
• global external Application Load Balancer depends on health check From the official documentation: “When these instances report an unhealthy status, they fail the load balancing health check, prompting the load balancer to stop directing traffic to these instances.”
• global external Application Load Balancer works with health check From the official documentation: “- [Health check](/load-balancing/docs/health-check-concepts): a policy used by the load balancer to evaluate the responsiveness of the application on each VM instance.”
• global external Application Load Balancer works with managed instance group From the official documentation: “The managed instance group provides VMs that run the backend servers of an external Application Load Balancer.”
• health check works with managed instance group From the official documentation: “Create an HTTP health check for port 80. This health check is used to verify the health of backends in the `ig-a` instance group.”