surge upgrades

Related topics

• Cluster Autoscaler works with surge upgrades From the official documentation: “Surge upgrades also work with the cluster autoscaler to prevent changes to nodes that are being upgraded.”
• surge upgrades depends on Compute Engine From the official documentation: “Unlike node recreation, surge upgrades require additional Compute Engine resources.”
• surge upgrades depends on Node Auto-Provisioning From the official documentation: “To change surge upgrade settings, you must configure cluster-level node auto-provisioning.”
• Cloud Logging works with GKE From the official documentation: “Enable Cloud Logging on GKE Clusters”
• Cloud Monitoring works with GKE From the official documentation: “Enable Cloud Monitoring on GKE Clusters”
• Compute Engine is an alternative to GKE From the official documentation: “You can also deploy a third-party model to either Vertex AI Model Garden or self-host on GKE or Compute Engine.”
• Cloud Logging works with Cloud Monitoring From the official documentation: “You can store and view query-response activity logs in Cloud Logging and set up logs-based monitoring by using Cloud Monitoring.”
• Cloud Logging works with Compute Engine From the official documentation: “Compute Engine sends you Cloud Logging events for scheduled, started, or completed maintenance.”
• Compute Engine is an alternative to Google Kubernetes Engine From the official documentation: “You can install MongoDB on a Compute Engine instance or you can deploy MongoDB on Google Kubernetes Engine.”
• GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
• Cloud Logging works with Google Kubernetes Engine From the official documentation: “By default, GKE clusters send system log data and system metric data to Logging and Monitoring.”
• Cloud Monitoring works with Cluster Autoscaler From the official documentation: “GKE cluster autoscaler exposes metrics to Cloud Monitoring that provide insights into its decisions, especially in relation to ComputeClasses.”
• Cloud Monitoring works with Google Kubernetes Engine From the official documentation: “When Google Kubernetes Engine (GKE) [system metrics](/kubernetes-engine/docs/how-to/configure-metrics#system-metrics) are enabled, Cloud Monitoring collects the following metrics.”
• Cluster Autoscaler is part of GKE From the official documentation: “GKE's *cluster autoscaler* automatically resizes the number of nodes in a given node pool, based on the demands of your workloads.”
• Cluster Autoscaler is part of Google Kubernetes Engine From the official documentation: “Google Kubernetes Engine: [Cluster autoscaler](/kubernetes-engine/docs/concepts/cluster-autoscaler) and [node auto-provisioning](/kubernetes-engine/docs/how-to/node-auto-provisioning)”
• 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.”
• managed instance group works with Spot VMs From the official documentation: “This document explains how to create a managed instance group (MIG) that uses Spot VMs.”
• Spot VMs is part of Compute Engine From the official documentation: “Spot VMs are virtual machine (VM) instances that are excess Compute Engine capacity.”
• Cloud Logging is an alternative to Cloud Monitoring From the official documentation: “To see the status of your invalidation request or find a definitive list of recently submitted requests, you can use Cloud Logging or Cloud Monitoring.”
• Cloud Logging works with Cluster Autoscaler From the official documentation: “The cluster autoscaler emits events detailing scale-up, scale-down, and other significant decisions. These events are available as log entries in Cloud Logging.”
• Cloud Monitoring works with Compute Engine From the official documentation: “Many Google services like Compute Engine send telemetry to Cloud Monitoring.”
• Cluster Autoscaler works with Google Kubernetes Engine From the official documentation: “Configure the [cluster autoscaler](/kubernetes-engine/docs/concepts/cluster-autoscaler) and [node auto-provisioning](/kubernetes-engine/docs/how-to/node-auto-provisioning) to adjust the node count based on pending Pod resource requests like CPU, memory, GPU, and Cloud TPU.”
• Cluster Autoscaler configures managed instance group From the official documentation: “Cluster autoscaler increases or decreases the size of the node pool automatically by adding or removing virtual machine (VM) instances in the underlying Compute Engine [Managed Instance Group (MIG)](/compute/docs/instance-groups#managed_instance_groups) for the node pool.”
• Cluster Autoscaler works with Spot VMs From the official documentation: “Both the cluster autoscaler and node auto-provisioning support using Spot VMs.”
• Compute Engine works with Google Kubernetes Engine From the official documentation: “Compute Engine integrates with Google Cloud technologies such as Cloud Storage, Google Kubernetes Engine, and BigQuery, to extend beyond the basic computational capability to create more complex and sophisticated applications.”
• Google Kubernetes Engine works with Node Auto-Provisioning From the official documentation: “Configure the [cluster autoscaler](/kubernetes-engine/docs/concepts/cluster-autoscaler) and [node auto-provisioning](/kubernetes-engine/docs/how-to/node-auto-provisioning) to adjust the node count based on pending Pod resource requests like CPU, memory, GPU, and Cloud TPU.”
• Node Auto-Provisioning is part of GKE From the official documentation: “With node auto-provisioning, GKE automatically provisions node pools based on cluster resource demand.”
• Node Auto-Provisioning is part of Google Kubernetes Engine From the official documentation: “Google Kubernetes Engine: [Cluster autoscaler](/kubernetes-engine/docs/concepts/cluster-autoscaler) and [node auto-provisioning](/kubernetes-engine/docs/how-to/node-auto-provisioning)”
• Node Auto-Provisioning depends on Google Kubernetes Engine From the official documentation: “To enable node pool auto-creation for the entire cluster, you enable the *node auto-provisioning* feature for the cluster by using the Kubernetes Engine API.”
• Node Auto-Provisioning works with Spot VMs From the official documentation: “Both the cluster autoscaler and node auto-provisioning support using Spot VMs.”