-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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 multi-project clusters on GCE #191
Comments
Curious as to whether we heard about this use case from users and any more details they might have reported. |
This came out of a conversation about where the configuration for the project field should be stored in PR #183 |
Got it. It seems like no specific example was mentioned, just as a general possibility. Let's keep this issue open to gather more input. |
This issue was moved to kubernetes-sigs/cluster-api-provider-gcp#35 |
Controller cleanup
🐛Fix NPE when looking at Cluster Network fields
Once PR #183 is merged, a single project for a cluster is defined in the GCEClusterProviderConfig. Only a single project is supported. This issue is to allow the GCEClusterProviderConfig to take a list of projects that are supported for the cluster. Then each machine will need to define its own Project field in GCEMachineProviderConfig, which will be required to be in the list in GCEClusterProviderConfig.
Provisioning of networks, firewall rules and service account permissions will be impacted by this change.
The text was updated successfully, but these errors were encountered: