-
Notifications
You must be signed in to change notification settings - Fork 28
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
FeatureReq: Simpler optional gcloud LandingZone - combined perimeter + client-landing-zone for non-managed clients - 3 VPC (2 for fortigate cluster) #843
Comments
starting deployment of https://github.com/fortinet/fortigate-tutorial-gcp via fork for adjustments/PRs in |
following last Oct 2022 run in fortinet/fortigate-tutorial-gcp#1
|
switching repos
follow get compute quota increased 5-10
manually enable service - add to PR
License setup - register licenses first for byod |
todo
https://support.fortinet.com/asset/#/views/products/detail;from=%252Fviews%252Fproducts
|
tutorial-vars.sh changes
tutorial-create.sh adjustments
https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/blob/main/solutions/project/hub-env/setters.yaml#L53C66-L53C113
see run
|
0745 run - eta 45 min
but script change did with instance id and m*s1 as pw
758
0803
|
testing
|
diff
|
verify alternate ip address on elb/ilb - for routing to work |
Normally we run the 4 packages core-lz, client-setup, client-lz, client-project-setup and then the hub-env package around the following architecture which stands up 1 VPC for the client and 4 for the hub-env
https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/wiki/Architecture
Client requires a non-managed landing zone consisting of a single VPC containing both the perimeter firewall and the client workloads.
This LZ is a one-off LZ per client - unmanaged
An alternative to peering the client-landing-zone host-project with this hub-env project in #847
However peering is unavoidable as the example fortigate deployment needs 2 min for the dual LB version.
proposed gcloud only
start with base fortinet script - except this one is 3 VPC with 2 for the fortigate cluster (internal LB is in its own subnet) + 1 for the workloads
https://github.com/fortinet/fortigate-tutorial-gcp/blob/main/gcloud/tutorial-create.sh
see
fortinet/fortigate-tutorial-gcp#1
fortinet/fortigate-tutorial-gcp#5
Current hub-env VPCs are 4
https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/blob/main/solutions/project/hub-env/network/vpc.yaml#L15
check hardcoded management subnet
and docs
https://docs.fortinet.com/document/fortigate-public-cloud/7.4.0/gcp-administration-guide/736375/about-fortigate-vm-for-gcp
The text was updated successfully, but these errors were encountered: