(cloud.google.com)

1. dsign ◴[18 Feb 20 16:59 UTC] No.22357478[source]▶

Can those instances be used in GKE node pools?

2. boulos ◴[18 Feb 20 17:16 UTC] No.22357688[source]▶

Disclosure: I work on Google Cloud.

Should be, once the rollouts complete. So once you can see N2D types in the Console for your project, I think it'll just flow naturally to GKE.

replies(1): >>22357724 #

3. cvallejo ◴[18 Feb 20 17:19 UTC] No.22357724[source]▶

>>22357688 #

Disclosure: I also work on Google Cloud

That's correct! Once the rollout completes, you will be able to use N2D instances for GKE!

replies(2): >>22357787 #>>22358026 #

4. p_l ◴[18 Feb 20 17:23 UTC] No.22357787{3}[source]▶

>>22357724 #

And if it doesn't, it was always possible to break GKE state into "offering" node types that were not supported. Source: me, using preemptible instances for a year before they got into GKE ;-)

Modifying instance group templates is your friend.

replies(1): >>22362049 #

5. simonebrunozzi ◴[18 Feb 20 17:39 UTC] No.22358026{3}[source]▶

>>22357724 #

> Disclosure: I also work on Google Cloud

Wow, half of the comments so far start with this disclosure! Tons of Google people lurking on HN :)

replies(1): >>22358180 #

6. gpm ◴[18 Feb 20 17:50 UTC] No.22358180{4}[source]▶

>>22358026 #

Too be fair, it's just two of them answering questions, and one is both OP and the product manager.

7. crazysim ◴[19 Feb 20 00:52 UTC] No.22362049{4}[source]▶

>>22357787 #

Yeah, this can be done for nested virtualization instances (images) too.

8. leemoonsoo ◴[19 Feb 20 01:13 UTC] No.22362184[source]▶

>>22357478 (TP) #

When gVisor is enabled, hyper-threading is disabled (https://cloud.google.com/kubernetes-engine/docs/concepts/san...) and GKE cluster shows only half the CPU as available resources.

Does n2d instance is considered safe from CPU vulnerability and safely enable hyper-threading when used with gVisor?

↑

New AMD EPYC-based Compute Engine family, now in beta