The GCP PubSec Declarative Toolkit is a collection of declarative solutions to help you on your Journey to Google Cloud. Solutions are designed using Config Connector and deployed using Config Controller.
Describe the bug
For those KCC solutions with RootSync resources included in the solution package, there is a conflict that the RootSync manages itself in the same repo after pushing to git repo and using RootSync to gitops the solution.
nomos status --contexts gke_${PROJECT_ID}_northamerica-northeast1_krmapihost-${CLUSTER}
Step5: Found the error as shown below.
Expected behavior
RootSyncs resources can be stored with the solution code at the same repo and different folder and Root Sync resources are deployed separately.
Describe the bug For those KCC solutions with RootSync resources included in the solution package, there is a conflict that the RootSync manages itself in the same repo after pushing to git repo and using RootSync to gitops the solution.
To Reproduce Step1: Follow the below guide to deploy core landing zone v2. https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/blob/main/docs/landing-zone-v2/README.md Step2: Follow the below guide to deploy client setup solution. https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/blob/main/solutions/client-setup/README.md Step3: Validate the Root Syncs resource are located in the solution package at the git repo.
Step4: Validate deployment by the below command.
Step5: Found the error as shown below.
Expected behavior RootSyncs resources can be stored with the solution code at the same repo and different folder and Root Sync resources are deployed separately.