←back to thread

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

(cloud.google.com)
343 points cvallejo | 2 comments | 18 Feb 20 16:31 UTC | HN request time: 0.449s | source
Show context
dsign ◴[18 Feb 20 16:59 UTC] No.22357478[source]▶
Can those instances be used in GKE node pools?
replies(2): >>22357688 #>>22362184 #
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 #
cvallejo ◴[18 Feb 20 17:19 UTC] No.22357724[source]▶
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 #
1. p_l ◴[18 Feb 20 17:23 UTC] No.22357787[source]▶
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 #
2. crazysim ◴[19 Feb 20 00:52 UTC] No.22362049[source]▶
Yeah, this can be done for nested virtualization instances (images) too.