-
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
Demo: Script: Automated minimal landing zone with a (hub-env and core-landing-zone, client-setup, client-landing-zone, client-project-setup) GitOps/OCI based deployment on a clean GCP organization - walkthrough #766
Comments
docs adjust
|
walkthrough triage and issues spawnFollow monorepo instructions from SSC around the hydration script (wraps kpt fn render)
|
move the partially completed kpt version script in 446 that completed the core-landing-zone and was mid way through hub-env
|
Clean org 2 - cloud-setup.orgAdd IAM permissions to be able to create a project at the org or folder levelWe need this before we can clone the script and continue from there
Create folder
Create bootstrap project - default at the org level
Associate billing
|
|
triage skipped resources on pass 1
missing 12
|
rerunning apply for 12 services
checking
check the cluster
reference |
review 0.7.0 issue in dec #752 |
recheck cluster - time heals - just needed an extra hour
|
update failed to fix 12 on this particular cloud-setup org - like oi did - removing and redeploying core-landing-zone
clean up
increment prefix in vars.sh - for projects and buckets
rerun
|
1202 - better
Same issue on redeployed cloud-setup
https://cloud.google.com/storage/docs/access-control/iam-roles
added to #801 |
subnets should be of the form without project prefix - see #830 tried michael@cloudshell:~/kcc-cso/kpt (kcc-cso-4380)$ kubectl get gcp -n client1-hierarchy needs to be the same as [clients.clientnam](kpt-set: clients.${client-name})
forgot same rootsync folder needs deleting
|
client-project-setup
|
add to setup.sh - Anoop's RBAC addition in |
update LZ with package updates
|
Retesting hub-env automation
instances up in 5 min fgt-primary-instance | northamerica-northeast1-a | | | 172.31.200.10 (nic0) 172.31.201.10 (nic1) 172.31.203.10 (nic2) 172.31.202.10 (nic3) | | SSH | |
|
hub-env status
single failure on the nat
|
raised separate #837 |
Fixing permissions issue on compute for client project |
Moving billing for hub-env project to another billing id |
Nat issue fixed by adding a restrictCloudNATUsage project level override for hub-env in #837 |
verify alternate ip address on elb/ilb - for routing to work check sdnconnector or ha remember sync ilb custom config int hub-env research vdom - one also for management vm - which interface to update from fortinet real locked license - sharable? plan: 5 + separate hub-env pipelines |
git merge main |
see
https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/wiki/DevOps
Base architecture with GCP native firewalls
Cluster with 4 packages clz + 4 client
Extended version with Fortigate NGFW
including projects/hub-env package
mermaid - diagrams as code
Issues
Infrastructure
Follow docs starting at https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/tree/main/docs/landing-zone-v2#3-deploy-the-infrastructure-using-gitops
Follow wiki - https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/wiki/DevOps#landing-zone-install
Follow triage - https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/wiki/DevOps#workaroundstriage
Update https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/wiki/DevOps#monorepo-lz
Follow monorepo instructions from SSC around the hydration script (wraps kpt fn render)
This is the OCI (repo tracking) version of deployment - not the minimal KPT based deployment in #611
Architecture
https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/wiki/Architecture
Inventory
Package: core-landing-zone
Package: client-setup
Package: client-landing-zone
Package: client-project-setup
Package: projects/hub-env
Package: gatekeeper-policies
Minimal Landing Zone from a clean GCP organization using a single script - use for development or CI/CD
FinOps: PAYG + GKE + GCE costs will be $80/day above the normal $10/day for the GKE cluster alone.
This jira will document standing up a subset of the full landing zone consisting of the following 2 packages in a clean org
References
See ongoing documentation in
https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/wiki/DevOps#landing-zone-user-procedures
Clean Organization
Clean super admin
The super admin account will have the organization administrator role and be able to create projects through the project creator role on the organization (all users inherit this and we will lock it down later)
Launch shell.cloud.google.com
navigate to https://shell.cloud.google.com
By default the user is an Organization Administrator
We will add required roles to get the point of creating a bootstrap project and then let the landing zone setup script take over adding roles required for LZ bootstrap.
For those customers on direct billing - activate your credits
5 billing projects required
Prepare for increasing billing quota above 5 projects by paying early $50 and asking for a billing quota increase 2 days later - for how use shared billing to go past 5. For the purposes of the core-landing-zone and hub-env you need 1 bootstrap project, 1 config controller project, a logging and dns project and a hub project. Therefore disable billing on "My first project" to have all 5 for now.
follow instructions to increase your billing account quota to above 10 (I asked for 10 in addition to the default 5) using our instructions below
https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/wiki/Onboarding#billing-quota
fill out
https://support.google.com/code/contact/billing_quota_increase
Usually you are approved within 60 seconds
license key config
https://github.com/fortinetsolutions/terraform-modules/blob/master/GCP/modules/fortigate_byol/main.tf#L33
see also
https://cloud.google.com/architecture/managing-cloud-infrastructure-using-kpt
The text was updated successfully, but these errors were encountered: