-
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
[BUG]: sm: During kpt live apply - 4 CRDs are missing from the CC GKE cluster - NamingPolicy, DataLocation, LimitEgressTraffic, CloudMarketPlaceConfig #103
Comments
Easiest would be to add the policy directory to the |
nice, rerunning with "Easiest would be to add the policy directory to the .krmignore file" add to faq |
Full fix is .krmignore filter cicd-examples/ results We progressed to the LZ projects coming up - i will document an additional DOC / FEATURE on pre-increasing the billing/project quota on new accounts
|
After bringing up a new cluster on obrienlabs.dev in #94 (comment) for #104 https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/tree/main/solutions/landing-zone
using --inventory-policy adopt via kptdev/kpt#1724
|
I agree, move to the readme or use something more granular than the entire folder. and your |
Again there is not much we can do to remediate this in the |
Understood, I am attempting to document and/or workaround getting the landing-zone solution up before starting to modify it |
Closing this issue and moving discussion to #114 . |
Use case: LZ deploy section 5 - kpt
https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/tree/main/solutions/landing-zone#usage
part of #33
see setters.yaml in #99
We need to run from the parent dir
The text was updated successfully, but these errors were encountered: