-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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 Google Virtual Network Interface (gVNIC) #7699
Add support for Google Virtual Network Interface (gVNIC) #7699
Comments
This doesn't exist in the generated go client yet. https://raw.githubusercontent.com/googleapis/google-api-go-client/master/compute/v0.beta/compute-gen.go and search for "type NetworkInterface" Also:
https://pkg.go.dev/google.golang.org/api/compute/v0.beta#NetworkInterface |
Moving into Sprint 26 for the assignee to re-investigate. We can move this back out if it's still not available. |
Using pre-configured images works (like below) boot_disk {
initialize_params {
image = "beta/projects/gvnic-vm-image-prod/global/images/family/debian-9-gvnic"
}
} |
note: I filed this issue describing a part of the upcoming GA API, which doesn't appear to be a part of the beta API. Whoops! At beta, we just need to ensure we can enable gvnic under |
@edwardmedia: The instance part of this API should be available now. When you have the chance, mind giving it a try? |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
Community Note
Description
https://cloud.google.com/compute/docs/instances/create-vm-with-gvnic
Will appear as the
networkInterfaces[].nicType
field, which doesn't currently appear in the docsNew or Affected Resource(s)
Potential Terraform Configuration
References
The text was updated successfully, but these errors were encountered: