After you have set up a Google Cloud foundation using the setup guide, you can find and manage your foundation in two different locations:
Manage your foundation using the Google Cloud console
Because many different people at an organization are responsible for managing Google Cloud infrastructure after deployment, the Google Cloud console features separate pages for billing, resource management, identity and access management, networking, logging, monitoring, as well as many other services.
To get started with managing your foundation in the Google Cloud console, visit the following pages:
- Go to Resource Manager
- Go to Identity and Access Management
- Go to Network services
- Go to Cloud Logging
- Go to Cloud Monitoring
Each of the preceding pages has a robust interface for managing and making changes, as well as corresponding documentation and tutorials.
Manage your foundation using Config Controller
If you deployed your foundation directly from the Google Cloud foundation setup guide, this created a blueprint that represents your configuration in the Kubernetes Resource Model (KRM) format. If you want to manage your Google Cloud organizational configuration using KRM, which is the same underlying tooling used for initial deployment, you can use Config Controller to manage your foundation. You can also locate and manage your foundation using the Google Cloud console.
If you used the Google Cloud setup guide, downloaded your configuration as Terraform, and deployed it from your own machine, use the Google Cloud console to locate and manage your foundation.
The following sections show you how to complete the following tasks:
- Set up Config Controller and a GitOps pipeline. These are the KRM blueprint tools that you need to manage your foundation.
- Load your initial KRM configuration. This is the configuration that was created when you set up your Google Cloud foundation.
- Make KRM configuration updates.
- Deploy an updated KRM configuration.
- Troubleshoot common situations.
The following instructions require you to use several Google Cloud products. Each has associated costs. To learn more, see the following articles:
- Config Controller costs
- Cloud Build costs
- Cloud Source Repositories costs
- Cloud Storage buckets costs
Adjust your Google Cloud foundation configuration
After successfully deploying your Google Cloud foundation from the Google Cloud setup guide complete the following steps to adjust your configuration:
Open Cloud Shell:
Go to the Google Cloud console.
From the upper-right corner of the console, click the Activate Cloud Shell button:
A Cloud Shell session opens inside a frame lower on the console.
Find the project created by the Google Cloud setup guide. This is where the blueprint is located:
gcloud projects list --filter labels.gcp-onboarding-component=oc-host-project \ --filter labels.gcp-onboarding-host-project-org-id=ORG_ID
ORG_IDwith your organization ID. If you don't know what this value is, see Getting your organization ID.
From the output of the preceding command, copy the project ID. You need to use this value when you complete the next two steps.
Set up a GitOps pipeline by completing the Creating a GitOps pipeline section in Deploy a landing zone blueprint.
Navigate to the Google Cloud setup guide.
Go to the Resource & Hierarchy section and make a copy of the Configuration link. This is the link to the Cloud Storage bucket containing the deployed blueprint:
Download the KRM blueprint to your local filesystem:
gsutil -m cp -r BLUEPRINT_LOC .
BLUEPRINT_LOCwith the storage bucket link that you copied in the previous step.
Commit the KRM blueprint to your repository. This blueprint is the baseline for the configuration you’ve already deployed:
git add . git commit -m "Baseline configuration." git push
To achieve the configuration that you want, make local edits to the blueprint. For suggestions on the type of changes that you can make, see Setting up your resource hierarchy, Establishing network connectivity, and Exporting logging data.
To deploy your changes, add and commit them to your repository:
git add . git commit -m "Local edits to blueprint" git push