-
Notifications
You must be signed in to change notification settings - Fork 87
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
Support for provisioning Gardener with Shared VPC in GCP #291
Comments
@kapilraju You have mentioned internal references in the public. Please check. |
Duplicate of #262? |
@prashanth26 Yes, this duplicate of #262 |
/close in favour of #262 |
@prashanth26 Can you please reopen this and close #262 , i don't have edit privilege for #262 to make changes to that post |
Do you need any additional information to consider this feature request? |
But you can comment which is fine. |
Is there any specific reason for this? If it's to add more description, feel free to comment on the other issue.
No. We will try to pick this up. |
/area networking
/kind enhancement
/priority 1
/platform gcp
What would you like to be added:
Gardener doesn't support creating Kubernetes cluster using GCP shared VPC. It fails to create the cluster because gardener cannot detect exported subnets(shared-vpc) in GCP service project and it detects only VPCs created locally in the service project
Why is this needed:
Shared VPC lets organization administrators to delegate administrative responsibilities to Service Project Admins(such as creating and managing instances) while maintaining centralized control over network resources like subnets, routes, and firewalls.
Using Shared VPC is also a Google recommended architecture
The text was updated successfully, but these errors were encountered: