Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
Nesta página, explicamos como fazer upgrade da versão do Config Sync instalada nos
clusters.
Fazer upgrade manual do Config Sync
Para ficar dentro da janela de suporte, recomendamos que você faça upgrade pelo menos a cada nove meses. No entanto, você pode fazer upgrade com mais frequência para ter os recursos e as atualizações de segurança mais recentes.
Fazer upgrade de uma versão sem suporte
Se a versão do Config Sync não tiver suporte, tente fazer upgrade usando uma das seguintes opções:
(Recomendado) Faça um upgrade passo a passo com incrementos de, no máximo,
duas versões secundárias por vez. Por exemplo, se você estiver na versão N-4 (uma versão sem suporte), faça upgrade para N-2 (uma versão com suporte) e depois para N (uma versão com suporte). Essa abordagem é o método mais seguro para fazer upgrade, mas só funciona se o primeiro upgrade incremental for para uma versão compatível.
Faça upgrade diretamente para uma versão aceita. Se não for possível fazer um upgrade
gradual, tente fazer upgrade diretamente para uma versão compatível. Por exemplo, se você estiver na versão N-6 (sem suporte), não será possível fazer um upgrade incremental para N-4 (sem suporte). Nesse
cenário, tente fazer upgrade diretamente para N-2 (a versão mais antiga compatível).
Se a versão do Config Sync estiver muito desatualizada e as opções anteriores não funcionarem, desinstale e reinstale o Config Sync.
Fazer upgrade do Config Sync
Antes de fazer upgrade do Config Sync, consulte as notas da versão para detalhes sobre o que foi alterado entre
as versões.
Para fazer upgrade do Config Sync, siga estas etapas:
Console
No console Google Cloud , acesse a página Configuração na seção Recursos.
VERSION: a versão para a qual você quer fazer upgrade
MEMBERSHIP_NAME: o nome da assinatura da frota que você escolheu
quando registrou o cluster. Para encontrar o nome da assinatura, execute
gcloud container fleet memberships list.
Fazer upgrade automático do Config Sync
Desativar upgrades automáticos
Para desativar os upgrades automáticos do Config Sync, siga estas etapas:
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-08-31 UTC."],[],[],null,["# Upgrade Config Sync\n\nThis page explains how to upgrade the Config Sync version installed on your\nclusters.\n\nManually upgrade Config Sync\n----------------------------\n\nTo stay within the\n[support window](/kubernetes-engine/enterprise/config-sync/docs/get-support-config-sync#recommended_version),\nwe recommend that you upgrade at least every nine months. However, you can\nupgrade more frequently to get the latest features and security updates.\n\n### Upgrade from an unsupported version\n\nIf your version of Config Sync is unsupported, you can try to upgrade it by\nusing one of the following options:\n\n- (Recommended) Perform a step-by-step upgrade with increments of no more than two minor versions at a time. For example, if you're on version N-4 (an unsupported version), you should upgrade to N-2 (a supported version), and then you can upgrade to N (a supported version). This approach is the safest method to upgrade, but only works if the first incremental upgrade is to a supported version.\n- Upgrade directly to a supported version. If you can't perform a step-by-step upgrade, you can try upgrading directly to a supported version. For example, if you're on version N-6 (an unsupported version), trying to perform an incremental upgrade to N-4 (an unsupported version) won't work. In this scenario, you can try upgrading directly to N-2 (the earliest supported version).\n- If your Config Sync version is significantly behind, and the previous options don't work, you can uninstall and reinstall Config Sync.\n\nUpgrade Config Sync\n-------------------\n\nBefore you upgrade Config Sync, check the\n[release notes](/kubernetes-engine/enterprise/config-sync/docs/release-notes) for\ndetails on what's changed between versions.\n| **Note:** If you use Config Controller to install and manage Config Sync, you don't need to manually upgrade. Config Controller is a managed service, so Google upgrades it automatically. For details on Config Controller changes, see the [Config Controller release notes](/kubernetes-engine/enterprise/config-controller/docs/release-notes).\n\nTo upgrade Config Sync, complete the following steps: \n\n### console\n\n1. In the Google Cloud console, go to the **Config** page under the **Features** section.\n\n \u003cbr /\u003e\n\n [Go to Config](https://console.cloud.google.com/kubernetes/config_management)\n2. Under the **Settings** tab, next to the cluster whose Config Sync version you want to upgrade, select **Edit cluster config**.\n3. From the **Version** drop-down list, select the version that you want to upgrade to.\n4. Click **Upgrade Config Sync**.\n\n### gcloud\n\n1. (Optional) If you want to check which Config Sync version is installed on your clusters before you upgrade, run the following command:\n\n gcloud beta container fleet config-management version\n\n2. Run the following command:\n\n gcloud beta container fleet config-management upgrade \\\n --version=\u003cvar translate=\"no\"\u003eVERSION\u003c/var\u003e \\\n --membership=\u003cvar translate=\"no\"\u003eMEMBERSHIP_NAME\u003c/var\u003e\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eVERSION\u003c/var\u003e: the version that you want to upgrade to.\n - \u003cvar translate=\"no\"\u003eMEMBERSHIP_NAME\u003c/var\u003e: the fleet membership name that you chose when you registered your cluster. You can find the membership name by running `gcloud container fleet memberships list`.\n\nAuto-upgrade Config Sync\n------------------------\n\n| **Caution:** The Config Sync auto-upgrades feature is unavailable starting in Config Sync version 1.21.0. You can no longer configure auto-upgrade settings and must [manually upgrade the Config Sync version](/kubernetes-engine/enterprise/config-sync/docs/how-to/upgrade-config-sync#manually-upgrade). If you currently use auto-upgrades, you must first [disable auto-upgrades](/kubernetes-engine/enterprise/config-sync/docs/how-to/upgrade-config-sync#disable-auto-upgrades) before you can manually update Config Sync.\n|\n| **Preview**\n|\n|\n| This product or feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA products and features are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n\n### Disable auto-upgrades\n\nTo disable Config Sync auto-upgrades, complete the following steps:\n**Important:** You can't disable Config Sync auto-upgrades through the Google Cloud console. Use the gcloud CLI or Terraform instructions instead. \n\n### gcloud\n\nRemove the `upgrades` field from your [Google Cloud CLI `apply spec`\nfile](/kubernetes-engine/enterprise/config-sync/docs/reference/gcloud-apply-fields#config_sync).\n\n### Terraform\n\nSet the `configmanagement.management` field to `MANAGEMENT_MANUAL` in the\n[google_gke_hub_feature_membership](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/gke_hub_feature_membership#configmanagement-1)\nresource.\n| **Important:** Don't remove the `configmanagement.management` field from the `google_gke_hub_feature_membership` resource. Removing the field doesn't disable Config Sync auto-upgrades since Terraform can't detect the change.\n\n### Config Connector\n\nSet the `configmanagement.management` field to `MANAGEMENT_MANUAL` in the\n[`GKEHubFeatureMembership`](/config-connector/docs/reference/resource-docs/gkehub/gkehubfeaturemembership)\nresource.\n| **Important:** Don't remove the `configmanagement.management` field from the `GKEHubFeatureMembership` resource. Removing the field doesn't disable Config Sync auto-upgrades and causes the fields to become [externally-managed](/config-connector/docs/concepts/managing-fields-externally) instead of managed by Config Connector."]]
