-
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
Day0: Adjust KPT instructions around gatekeeper policies apply missing 4 policies - skip directly to core-landing-zone #409
Comments
Thinking this could also be addressed in a way that resolves things for all installation types. Essentially have the For example the This breaks up the install and also makes it clearer as to what policies are being installed. |
@fmichaelobrien took a moment and made this demo branch in my fork to demonstrate, https://github.com/cartyc/pubsec-declarative-toolkit/tree/constraints-update/solutions/core-landing-zone . Moved the constraints out of gatekeeper policies and added a new folder to core-landing-zone that would hold the constraints. |
Reviewed, nice, thanks for the constraints move - will retest kpt when merged to main - will be ok |
See related kpt doc issue #429 |
We should also test |
Good idea cloud deploy integration - In the priority queue - in conversations with the CD team |
the original KPT docs Yes, since we removed the gatekeeper-policies and no longer just need the core-lz
I recommend a root init/render/apply like you mentioned Chris. |
https://cloud.google.com/architecture/managing-cloud-infrastructure-using-kpt 20230814: revisit kls
re-add kpt documentation at the end of section 2 https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/tree/main/docs/landing-zone-v2#2-create-your-landing-zone
kpt rendering ok
kpt live apply (20230414:1552)
just 1 org policy has an issue
|
I understand the KPT documentation will be removed from the readme and replaced by a separate alternative install - this issue is tracking a problem with the missing policies before we run the core-landing-zone. An understood chicken/egg issue but one that needs to be documented
the original KPT docs
https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/tree/solutions/core-landing-zone/0.3.0/docs/landing-zone-v2#kpt
Yes, since we removed the gatekeeper-policies and no longer just need the core-lz
I recommend a root init/render/apply like you mentioned Chris.
I also would like to just move to using cloud deploy for the deployment - in addition to using it for canary workload deployments - just need to find the time.
Document: skip the following step
https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/tree/main/docs/landing-zone-v2#gatekeeper-policies
see deployment notes on the day 0 install run in #296 (comment)
The text was updated successfully, but these errors were encountered: