Skip to content

GKE compute classes and update-variant #2358

@voron

Description

@voron

I've faced an unexpected issue while working on custom compute classes with manual GKE node pools. Custom compute class requires us to specify nodepool names, f.e

      ---
      apiVersion: cloud.google.com/v1
      kind: ComputeClass
      metadata:
        name: rpc-spot
      spec:
        priorities:
          - nodepools: [rpc-1-spot]
          - nodepools: [rpc-0-spot]

"Private cluster update variant" version of this module uses dynamic names of node pools to provide "create-before-destroy" option, leading to node pool names like rpc-0-spot-54a8 and rpc-1-spot-ab16.

Are any nice options to use compute classes together with update-variant ?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions