Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for C3 instances with IDPF network interfaces #1311

Open
JoelSpeed opened this issue Sep 17, 2024 · 1 comment
Open

Add support for C3 instances with IDPF network interfaces #1311

JoelSpeed opened this issue Sep 17, 2024 · 1 comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@JoelSpeed
Copy link

/kind feature

Describe the solution you'd like
[A clear and concise description of what you want to happen.]

Google C3 instances support a different kind of advanced network interface, called [IDPF|https://cloud.google.com/compute/docs/networking/using-idpf]. I would like to use this interface type with these instances via CAPG, and so, need to expose via the MachineTemplate a way to configure the type of the network interface.

At present, CAPG omits the NicType field from the compute.NetworkInterface, but, the default is GVNIC (Standard gcp network interface), this new interface is just IDPF.

We should add an enum value to the spec that allows this to be configured by end users.

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 17, 2024
@k8s-triage-robot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

3 participants