Sole-tenant nodes are physical Compute Engine servers that are dedicated to hosting VM instances only for your specific project. Use sole-tenant nodes to keep your instances physically separated from instances in other projects, or to group your instances together on the same host hardware.
Read creating sole-tenant nodes to learn how to create nodes and place your instances on those nodes.
Read sole-tenant node pricing to learn how to calculate prices and discounts for sole-tenant nodes.
Each node is associated with one physical server, and is the only node running on that server. Within your nodes, you can run multiple instances of various sizes without sharing the host hardware with other projects. You can specify node affinities between your nodes and the instances that you want to run on those nodes. Use these affinities to either group several workloads together on the same nodes or isolate your workloads from one another on different nodes to meet your data compliance requirements.
For example, some payment processing workloads might require physical isolation from other workloads or virtual machines in order to meet compliance requirements. Sole-tenant nodes ensure that your instances do not share host hardware with instances from other projects, but you can also use labels to specify how your instances are arranged on your nodes and separate instances with sensitive workloads into their own private nodes away from your other non-sensitive workloads.
n1-node-96-624 node type has 96 vCPUs and 624 GB of memory, and
is available in multiple zones. Nodes of this size can accommodate VM instances
with up to 96 vCPUs and 624 GB of memory, but you can also fill the node
with multiple smaller VM instances with various sizes including
custom machine types
and instances with
The instances that you run on your nodes must have at least two vCPUs. When a
node is full, you cannot schedule additional instances on that node.
To see a complete list of node availability, run the
gcloud command-line tool.
gcloud compute sole-tenancy node-types list
Periodically, Compute Engine will replace older node types with newer node types. When a node type is replaced, you will be unable to create node groups using the old node type, and must upgrade your node templates to use the new node types. As a best practice, you can configure your node templates to use flexible node type requirements. Read the creating node groups page to see examples of node templates with flexible node types.
Sole-tenant nodes are compatible with existing Compute Engine features:
- If your node's host system requires maintenance, the node and all of the instances on the node continue to operate while they live migrate to updated host hardware.
- Sustained use discounts and committed use discounts reduce the costs of your sole-tenant nodes. Read sole-tenant node pricing to learn how discounts apply to sole-tenant nodes.
- VPC networks work with instances running on sole-tenant nodes the same way that they work with normal VM instances. You can use VPC networks to establish network connections between sole-tenant instances and normal VM instances.
- Use custom machine types or predefined machine types to create instances on your sole-tenant nodes. Because you already pay for the vCPUs and memory of the node itself, you do not pay extra for these instances.
- Create managed instance groups on your node groups. Your managed instance groups can use autoscaling while running on sole-tenant nodes, but the node groups cannot automatically scale.
- Combine VMs with multiple machine types on each node. You can use a mix of different machine types and custom machine types on the same node until the node reaches its vCPU and memory limit, which is defined by the node type.
The following features are not available on sole-tenant nodes at this time:
- Machine types with fewer than two vCPUs:
- Shared-core machine types:
- Custom machine types with only 1 vCPU
- Shared-core machine types:
- Local SSDs
- Memory-optimized machine types