Shielded VMs

Related topics

• Shielded VMs is part of Compute Engine From the official documentation: “Shielded GKE Nodes are built on top of Compute Engine [Shielded VMs](/compute/shielded-vm/docs/shielded-vm).”
• Confidential Computing is an alternative to Shielded VMs From the official documentation: “To protect sensitive data and code during execution, use [Shielded VMs](/compute/shielded-vm/docs/shielded-vm) or [confidential computing](/confidential-computing/confidential-vm/docs/confidential-vm-overview) for training workloads.”
• Compute Engine is an alternative to GKE From the official documentation: “To use TPU7x, you can use Google Kubernetes Engine (GKE) or Compute Engine.”
• Confidential Computing secures Compute Engine From the official documentation: “Enable Confidential Computing for Compute Engine Instances”
• GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
• Confidential Computing is part of Compute Engine From the official documentation: “Confidential Computing is disabled on a Compute Engine instance.”
• Confidential VM is part of Compute Engine From the official documentation: “Confidential VM instances are a type of [Compute Engine](/compute/docs) virtual machine.”
• Compute Engine works with GKE From the official documentation: “For example, Google Kubernetes Engine (GKE) can cause usage in Compute Engine.”
• Confidential Computing secures GKE From the official documentation: “In Google Cloud, to provide stronger cryptographic isolation for your workloads and to protect data in use, we support [Confidential Computing](/confidential-computing) services for Compute Engine virtual machine (VM) instances and Google Kubernetes Engine (GKE) nodes.”
• Confidential VM is part of Confidential Computing From the official documentation: “Protect data in-use with Confidential VM, Confidential GKE, Confidential Dataflow, Confidential Managed Service for Apache Spark, and Confidential Space.”