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

feat!: Added support for multi-project GKE Hub registration #840

Conversation

JamesDuncanNz
Copy link
Contributor

@JamesDuncanNz JamesDuncanNz commented Mar 4, 2021

Added an optional variable HUB_PROJECT_ID which will allow you to specific a seperate
GCP project for the GKE HUB than the project the cluster is deployed to.

This included updating the 3 examples the leveraged the hub module.

Fixes #837

Added an optional variable HUB_PROJECT_ID which will allow you to specific a seperate
GCP project for the GKE HUB than the project the cluster is deployed to.

This included updating the 3 examples the leveraged the hub module.

Issue: #837
@JamesDuncanNz JamesDuncanNz requested a review from bharathkkb March 4, 2021 01:04
@JamesDuncanNz JamesDuncanNz requested review from Jberlinsky and a team as code owners March 4, 2021 01:04
@comment-bot-dev
Copy link

comment-bot-dev commented Mar 4, 2021

Thanks for the PR! 🚀
✅ Lint checks have passed.

Copy link
Member

@bharathkkb bharathkkb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR @JamesDuncanNz

examples/simple_zonal_with_hub/hub.tf Outdated Show resolved Hide resolved
modules/hub/scripts/gke_hub_registration.sh Outdated Show resolved Hide resolved
modules/hub/main.tf Outdated Show resolved Hide resolved
modules/hub/main.tf Outdated Show resolved Hide resolved
modules/hub/main.tf Outdated Show resolved Hide resolved
Ensuring that the Hub default Service Account exists
when adding a cluster from outside the hub project

Issue: #837
modules/hub/main.tf Outdated Show resolved Hide resolved
Copy link
Member

@bharathkkb bharathkkb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall LGTM
@JamesDuncanNz can you test an upgrade from previous hub version to this. There maybe a delete recreate op as we are changing create_cmd_gke_body and would be good to capture this in the upgrade guide as it may result in the de registration and subsequent registration during upgrade.

modules/hub/main.tf Outdated Show resolved Hide resolved
modules/hub/main.tf Show resolved Hide resolved
@bharathkkb bharathkkb changed the title Added support for multi-project GKE Hub registration feat!: Added support for multi-project GKE Hub registration Mar 9, 2021
@bharathkkb bharathkkb merged commit 6dc1eb1 into terraform-google-modules:master Mar 9, 2021
@release-please release-please bot mentioned this pull request Mar 9, 2021
CPL-markus pushed a commit to WALTER-GROUP/terraform-google-kubernetes-engine that referenced this pull request Jul 15, 2024
…m-google-modules#840)

* Added support for multi-project GKE Hub registration

Added an optional variable HUB_PROJECT_ID which will allow you to specific a seperate
GCP project for the GKE HUB than the project the cluster is deployed to.

This included updating the 3 examples the leveraged the hub module.

Issue: terraform-google-modules#837

* Adding service idenity resource for multi project deployments

Ensuring that the Hub default Service Account exists
when adding a cluster from outside the hub project

Issue: terraform-google-modules#837

* Fixing bharathkkb comments

Fixes terraform-google-modules#837

* Fix linting issue

* Removed Google project data souce

Issue: terraform-google-modules#837

* Adding upgrade documentation for this change.

* Lint updates on readme.

Co-authored-by: James Duncan <[email protected]>
Co-authored-by: Bharath KKB <[email protected]>
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 this pull request may close these issues.

Needs to use --gke-uri instead of --gke-cluster in a multi-project scenario
3 participants