Allow specifying the minimum CPU platform in GCPMachine spec

[itspngu]

/kind feature

Describe the solution you'd like
The GCPMachine spec allows specifying machine types, but some setups necessitate requesting a certain minimum CPU platform. This should be an optional field in the GCPMachine spec.

Anything else you would like to add:
GCP docs: https://cloud.google.com/compute/docs/instances/specify-min-cpu-platform#rest_1

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[itspngu]

/remove-lifecycle stale

[jayesh-srivastava]

Hi @itspngu , is this still open, if yes then I can take this up.

[itspngu]

Hi @itspngu , is this still open, if yes then I can take this up.

Hey @jayesh-srivastava! Yes, I just currently lack the time to work on it - feel free and thank you :)

The usecase I implied in the original description but somehow failed to point towards explicitly was using Confidential Compute with Cluster-API, you have to request "AMD Milan" as minimum CPU platform for that.

[jayesh-srivastava]

/assign

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[itspngu]

/remove-lifecycle stale