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

[Question] Using an IPV4_IPV6 stack type with compute instances #618

Open
codesue opened this issue Feb 23, 2024 · 3 comments · May be fixed by #638
Open

[Question] Using an IPV4_IPV6 stack type with compute instances #618

codesue opened this issue Feb 23, 2024 · 3 comments · May be fixed by #638

Comments

@codesue
Copy link

codesue commented Feb 23, 2024

SUMMARY

I would like to create a compute instance that uses an existing dual stack subnet, and I would like to be able to ssh into the machine using the IPV6 address. I've tried simply adding the existing subnet to the machine's network_interfaces using the subnet's selfLink, but when I do that, only the IPV4 address is listed on the machine. The access_config options seem rather limited, and I haven't figured out how to create a compute instance with an IPV4_IPV6 stack type with them. Is this supported? If so, do you have examples of how to do this?

ISSUE TYPE
  • Question
COMPONENT NAME

gcp_compute_instance

ADDITIONAL INFORMATION
@safaci2000
Copy link
Contributor

I think the config option of stack-type=IPV4_IPV6 is missing. I'm not sure if this would address this, but wonder if setting an instance template with IPV6 support would allow you to get past this limitation?

safaci2000 added a commit to safaci2000/google.cloud that referenced this issue Jul 17, 2024
safaci2000 added a commit to safaci2000/google.cloud that referenced this issue Jul 17, 2024
@safaci2000
Copy link
Contributor

safaci2000 commented Jul 17, 2024

I created a PR for this feature. This seems to work when I tested it against GCP locally. #638

Additionally, this branch: https://github.com/safaci2000/google.cloud/tree/feature/computeV6 has more changes that I needed to use personally to assign a static IPV6 address.

I'm not super familiar with the layout of this project, but this change worked for me.

safaci2000 added a commit to safaci2000/google.cloud that referenced this issue Dec 11, 2024
@safaci2000
Copy link
Contributor

I'd like to see if there's a blocker in getting the MR merged in or if there's anything I could do to help get that merged in. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants