You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat!: Added support for multi-project GKE Hub registration (#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: #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: #837
* Fixing bharathkkb comments
Fixes#837
* Fix linting issue
* Removed Google project data souce
Issue: #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]>
Copy file name to clipboardExpand all lines: docs/upgrading_to_v14.0.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,3 +41,13 @@ The module now uses the new ASM [installation script](https://cloud.google.com/s
41
41
- Supports migrations from open source Istio 1.7 or 1.8 to ASM
42
42
43
43
Please see the script page for up to date details.
44
+
45
+
### GKE Hub Register & Unregister behaviour has changed
46
+
47
+
The [Hub submodule](https://github.com/terraform-google-modules/terraform-google-kubernetes-engine/tree/master/modules/hub) now supports registering a cluster to a Hub that is in a separate project. This is via the introduction of the `hub_project_id`.
48
+
variable. If you specify this variable, the cluster will be registered to this project and the GKE cluster will be deployed in the project specified in the `project_id` variable.
49
+
50
+
To upgrade to the latest version, you will need to remove the state for the `run_destroy_command[0]` resource because, as of this release we register / unregister clusters using the `--gke-uri` option.
51
+
52
+
If you run into errors during upgrade, you can remove the state for the run_destroy_command resource by running:
53
+
`terraform state rm module.hub.module.gke_hub_registration.null_resource.run_destroy_command[0]`
0 commit comments