Installing Anthos Config Management

This page provides you with resources for installing the different components of Anthos Config Management. To learn more about Anthos Config Management, see Anthos Config Management overview.

Supported platforms and versions

For Anthos Config Management versioning and upgrade compatibility information, see Anthos version and upgrade support.

Enabling Anthos Config Management

Enable the Anthos API for your project:

Console

In the Google Cloud Console, go to the Anthos API page.

Go to the Anthos API page

  • Click Enable.

gcloud

Run the following command:

 gcloud services enable anthos.googleapis.com
 

Enable Anthos Config Management by completing the following steps.

Console

  1. In the Google Cloud Console, go to the Anthos Features page.

    Go to the Anthos Features page

  2. In the Config Management row, click Enable.

  3. In the confirmation window, click Enable Config Management.

gcloud

Run the following command:

 gcloud alpha container hub config-management enable

Installing Anthos Config Management components

The following pages show you how to install the different Anthos Config Management components:

The preceding components can all run within the same Anthos Config Management installation. If you do not have an Anthos entitlement, you can install the following components on the following products:

Resource requests

The following table lists Kubernetes resource requirements for Anthos Config Management components. For more information, see Managing Resources for Containers in the Kubernetes documentation.

Component CPU Memory
Config Management Operator 100m 20Mi
Policy Controller 100m 256Mi
Config Connector 250m 400Mi

Config Sync resource requests

The resource requests for Config Sync differ depending on which Config Sync features you are using.

Feature CPU Memory
Standard mode 460 m 310 Mi
Multi-repo mode 710 m + 260 m * (number of RootSync and RepoSync objects) 620 Mi + 210 Mi * (number of RootSync and RepoSync objects)
Hierarchy Controller 220 m 220 Mi

For a breakdown of Config Sync resource requests by component, see Resource requests in the Config Sync documentation.

What's next