Disable Hierarchy Controller

This page explains how to disable Hierarchy Controller so that you can upgrade Config Sync.

Hierarchy Controller is no longer available. Starting in version 1.20.0, Config Sync blocks upgrades if Hierarchy Controller is installed.

To determine how to disable Hierarchy Controller, inspect the kubectl ConfigManagement object or gcloud apply spec file and take an action that corresponds to the value in the following fields:

• hierarchyController.enablePodTreeLabels: if true, and you use hierarchical observability, don't proceed with the steps on this page. Instead, reach out to Cloud Customer Care for help removing Hierarchy Controller.
• hierarchyController.enabled: if true, follow the instructions on this page to disable Hierarchy Controller.

When you disable Hierarchy Controller, it deletes the Hierarchy Controller components in your cluster. It does not delete the Hierarchy Controller Custom Resource Definitions (CRD). You need to manually remove those CRDs using kubectl:

• HierarchyConfiguration
• HNCConfiguration
• SubnamespaceAnchor
• HierarchicalResourceQuota

To remove the Hierarchy Controller fields, review the instructions for the method that you used to install Hierarchy Controller:

gcloud

Remove the hierarchyController block from your Google Cloud CLI apply spec file.

Terraform

Remove the hierarchyController block from your Terraform resource.

Config Connector

Set Hierarchy Controller fields to false in the GKEHubFeatureMembership resource.

Important: Don't remove the Hierarchy Controller fields from the GKEHubFeatureMembership resource. Removing the fields doesn't disable Hierarchy Controller and causes the fields to become externally-managed instead of managed by Config Connector.

kubectl

Remove the hierarchyController block from the ConfigManagement object.