4 ms·
I've had difficulty parsing the guidance from Google for Google Kubernetes Engine here: https://cloud.google.com/kubernetes-engine/docs/security-bulletins#may-1
by AaronFriel 7y ago
I've had difficulty parsing the guidance from Google for Google Kubernetes Engine here: https://cloud.google.com/kubernetes-engine/docs/security-bulletins#may-14-2019 https://cloud.google.com/kubernetes-engine/docs/security-bul...
> Note that n1-standard-1 (the GKE default), g1-small and f1-micro VMs only expose 1 vCPU to the guest environment so there is no need to disable Hyper-Threading.
I'm wondering if they've decided to just eat the loss on the single vCPU nodes, and for vCPUs >= 2, they pass the decision on to the customer.
Or is there someone else's VM running on the other hyperthread?
Here's their guidance on machine types: https://cloud.google.com/compute/docs/machine-types https://cloud.google.com/compute/docs/machine-types
> For the n1 series of machine types, a vCPU is implemented as a single hardware hyper-thread on one of the available CPU Platforms.
- deleted 7y ago[deleted]