-
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
New Organization Day 0: walkthrough/automation example #296
Comments
20230814: update for kpt deployment option Onboarding:
|
2nd environment: kcc.landing.systems
move deployment.sh from #192 and retrofit for v2
current state before retrofit
|
LZ V2 install - follow
|
at line 194 |
* #192 - move deployment sh to v2 * #192 - move deployment sh to v2 * #298 - create script interconnect * #296 - lz2 doc validation to line 192 --------- Co-authored-by: Michael O'Brien <[email protected]>
Co-authored-by: Michael OBrien <[email protected]>
Align with ACM alignment across docs in #349 |
#402
|
returning from ssc-spc-ccoe-cei/gcp-tools#32
folder not rendered properly in folder.yaml
|
Add a link to the gcp-tools setup-kcc.sh script for config controller bootstrap
Move to kcc.landing.systems
raise #438 After 50 min the nodepool is up but the cluster nodes are not running yet workaround is to delete it (to preserve quota) and rerun it manually - or wait 55 min for the cluster to auto delete
2338 workloads still coming up 2341 2342 2343 2344 - 3 left 1 left 2345 (13 min)
|
installing lz
|
as part of a client session during an lz install
as part of a client session during an lz install
ongoing GoogleCloudPlatform#296 day0 instructions make the instructions clearer on the 2 step quickstart - to avoid client confusion - install the kcc cluster - install a default landing-zone-v2 - composed of core-landing-zone and experimentation/core-landing-zone
ongoing #296 day0 instructions
verified all link changes follow |
…uctions link (#443) * #296 - add core-lz instructions - post kcc install ongoing #296 day0 instructions make the instructions clearer on the 2 step quickstart - to avoid client confusion - install the kcc cluster - install a default landing-zone-v2 - composed of core-landing-zone and experimentation/core-landing-zone * #296 - adjust SSC contribution link
…dPlatform#441) as part of a client session during an lz install
…ding-zone pkg instructions link (GoogleCloudPlatform#443) * GoogleCloudPlatform#296 - add core-lz instructions - post kcc install ongoing GoogleCloudPlatform#296 day0 instructions make the instructions clearer on the 2 step quickstart - to avoid client confusion - install the kcc cluster - install a default landing-zone-v2 - composed of core-landing-zone and experimentation/core-landing-zone * GoogleCloudPlatform#296 - adjust SSC contribution link
…eady to review/merge (GoogleCloudPlatform#423) * GoogleCloudPlatform#296 - Update README.md with setup-kcc.sh link Add a link to the gcp-tools setup-kcc.sh script for config controller bootstrap * GoogleCloudPlatform#296 - update README.md grammer
…dPlatform#441) as part of a client session during an lz install
…ding-zone pkg instructions link (GoogleCloudPlatform#443) * GoogleCloudPlatform#296 - add core-lz instructions - post kcc install ongoing GoogleCloudPlatform#296 day0 instructions make the instructions clearer on the 2 step quickstart - to avoid client confusion - install the kcc cluster - install a default landing-zone-v2 - composed of core-landing-zone and experimentation/core-landing-zone * GoogleCloudPlatform#296 - adjust SSC contribution link
20231018: installing the projects/hub package in #446
recreation of lz from scratch in a new org - to verify script #611
deletion is in #593
20230714: to review
Short Sequence
20230523: udpate
Issues pending
20230503: update
Adjust in place the following script in the gcp-tools repo
https://github.com/ssc-spc-ccoe-cei/gcp-tools/blob/main/scripts/bootstrap/setup-kcc.sh
ssc-spc-ccoe-cei/gcp-tools#32
see ssc-spc-ccoe-cei/gcp-documentation#12
see #344
Older walk through
#33
Work Items:
General Docs
The text was updated successfully, but these errors were encountered: