hierarchyController.enablePodTreeLabels: jika true, dan Anda menggunakan
kemampuan observasi hierarkis,
jangan lanjutkan langkah-langkah di halaman ini. Sebagai gantinya, hubungi
Cloud Customer Care untuk mendapatkan bantuan terkait penghapusan Pengontrol Hierarki.
hierarchyController.enabled: jika true, ikuti petunjuk di
halaman ini untuk menonaktifkan Pengontrol Hierarki.
Saat Anda menonaktifkan Pengontrol Hierarki, komponen Pengontrol Hierarki akan dihapus di cluster Anda. Hal ini tidak
menghapus Definisi Resource Kustom (CRD) Pengontrol Hierarki. Anda
harus menghapus CRD tersebut secara manual menggunakan kubectl:
HierarchyConfiguration
HNCConfiguration
SubnamespaceAnchor
HierarchicalResourceQuota
Untuk menghapus kolom Pengontrol Hierarki, tinjau petunjuk
untuk metode yang Anda gunakan untuk menginstal Pengontrol Hierarki:
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-01 UTC."],[],[],null,["# Disable Hierarchy Controller\n\nThis page explains how to disable Hierarchy Controller so that you can\nupgrade Config Sync.\n\nHierarchy Controller is no longer available. Starting in version 1.20.0,\nConfig Sync blocks upgrades if Hierarchy Controller is installed.\n\nTo determine how to disable Hierarchy Controller, inspect the\n[`kubectl` `ConfigManagement` object](/kubernetes-engine/enterprise/config-sync/docs/configmanagement-fields)\nor [`gcloud` `apply spec` file](/kubernetes-engine/enterprise/config-sync/docs/reference/gcloud-apply-fields#hierarchy_controller)\nand take an action that corresponds to the value in the following fields:\n\n- `hierarchyController.enablePodTreeLabels`: if `true`, and you use [hierarchical observability](/kubernetes-engine/enterprise/config-sync/docs/how-to/observing-hierarchical-workloads#enable_hierarchical_observability), don't proceed with the steps on this page. Instead, reach out to [Cloud Customer Care](/support/docs) for help removing Hierarchy Controller.\n- `hierarchyController.enabled:` if `true`, follow the instructions on this page to disable Hierarchy Controller.\n\nWhen you disable Hierarchy Controller, it deletes the Hierarchy Controller\ncomponents in your cluster. It does not\ndelete the Hierarchy Controller Custom Resource Definitions (CRD). You\nneed to manually remove those CRDs using `kubectl`:\n\n- `HierarchyConfiguration`\n- `HNCConfiguration`\n- `SubnamespaceAnchor`\n- `HierarchicalResourceQuota`\n\nTo remove the Hierarchy Controller fields, review the instructions\nfor the method that you used to install Hierarchy Controller: \n\n### gcloud\n\nRemove the `hierarchyController` block from your\n[Google Cloud CLI `apply spec` file](/kubernetes-engine/enterprise/config-sync/docs/reference/gcloud-apply-fields#hierarchy_controller).\n\n### Terraform\n\nRemove the `hierarchyController` block from your\n[Terraform resource](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/gke_hub_feature_membership#argument-reference).\n\n### Config Connector\n\nSet Hierarchy Controller fields to `false` in the\n[`GKEHubFeatureMembership`](/config-connector/docs/reference/resource-docs/gkehub/gkehubfeaturemembership)\nresource.\n| **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](/config-connector/docs/concepts/managing-fields-externally) instead of managed by Config Connector.\n\n### kubectl\n\nRemove the `hierarchyController` block from the\n[`ConfigManagement` object](/kubernetes-engine/enterprise/config-sync/docs/configmanagement-fields)."]]
