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.

Sign up for GitHub

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

Jump to bottom

Subnets don't work when using an existing VPC for AWS #3804

Closed
ljupcovangelski opened this issue Oct 7, 2022 · 1 comment
Closed

Subnets don't work when using an existing VPC for AWS #3804

ljupcovangelski opened this issue Oct 7, 2022 · 1 comment
Assignees
@ljupcovangelski
Labels
infrastructure

Comments

@ljupcovangelski
Copy link
Contributor

When creating Airy with Terraform on an existing VPC, using the var.vpc_id parameter, the subnets are submitted as network IP subnets instead of subnet IDs.
ljupcovangelski added a commit that referenced this issue Oct 7, 2022
@ljupcovangelski
[#3804] Fix using existing subnets for AWS
1e8b2f3
@ghost ghost assigned ghost and ljupcovangelski and unassigned ghost Oct 11, 2022
ljupcovangelski added a commit that referenced this issue Oct 11, 2022
@ljupcovangelski
[#3804] Fix using existing subnets for AWS (#3812)
4c7ce7a 
* Fix using existing subnets for AWS
* Add name of GKE cluster in a variable
@ljupcovangelski
Copy link
Contributor Author

Resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ljupcovangelski ljupcovangelski

Labels
infrastructure
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ljupcovangelski