Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
A versão anterior dos clusters conectados do GKE é conhecida como clusters anexados ao GKE
(geração anterior). A migração da versão
anterior de clusters anexados ao GKE para a geração atual oferece acesso a essa
funcionalidade, incluindo o gerenciamento do ciclo de vida e o registro de frota. A migração
é uma operação de mão única: depois de migrar para a geração atual de
clusters anexados ao GKE, não é possível retornar aos clusters anexados ao GKE da geração anterior.
Política de numeração de versões
Esses documentos se referem à versão dos clusters anexados ao GKE como a versão da plataforma,
para diferenciá-la da versão do Kubernetes. Os clusters anexados ao GKE usam a mesma
convenção de numeração de versões que o GKE. Por exemplo, 1.21.5-gke.1. Ao anexar ou atualizar
seu cluster, escolha uma versão de plataforma em que a versão secundária seja igual
ou um nível abaixo da versão do Kubernetes do cluster. Por exemplo, é
possível anexar um cluster que executa o Kubernetes v1.22.* com a plataforma de clusters anexados
do GKE 1.21.* ou 1.22.*.
Isso permite fazer upgrade do cluster para a próxima versão secundária antes de fazer upgrade
dos clusters anexados ao GKE.
Verifique se a Identidade da carga de trabalho está ativada
Os clusters atuais dos clusters anexados do GKE (geração anterior) precisam ter a Identidade da carga de trabalho ativada antes de serem migrados para a geração atual dos clusters anexados do GKE.
Para determinar se o Wi-Fi está ativado, execute o seguinte comando e verifique a saída de qualquer campo de Identidade da carga de trabalho:
Se a Identidade da carga de trabalho não estiver ativada, a assinatura precisará ser atualizada para ativá-la.
O comando para atualizar a associação do cluster varia um pouco, dependendo
do cluster ter um emissor OIDC público ou particular. Escolha a guia
que se aplica ao cluster:
Execute o comando a seguir para migrar o cluster para a geração atual
de clusters anexados ao GKE. Esse comando extrai os detalhes relevantes da configuração do
cluster e o registra no gerenciamento de frotas do Google.
Ele instala ou faz upgrade de qualquer software necessário, como o agente do ciclo de vida, no
cluster.
GOOGLE_CLOUD_REGION: o local do Google Cloud
em que o cluster é administrado.
FLEET_MEMBERSHIP: o identificador de associação totalmente qualificado
do cluster registrado (confira abaixo)
PLATFORM_VERSION: a versão dos clusters anexados ao GKE para
a qual você quer migrar (exemplo: v1.22.0-gke.1)
CLUSTER_DISTRIBUTION: o tipo de cluster – eks para
o Elastic Kubernetes Service da AWS, aks para o Azure Kubernetes Service ou
generic para qualquer outra distribuição
KUBECONFIG_CONTEXT: o nome do contexto no
kubeconfig para se conectar ao cluster
KUBECONFIG_PATH: o local do seu arquivo kubeconfig.
Se não for especificado, o padrão será ~/.kube/config.
O identificador da associação é uma string que identifica exclusivamente seu cluster anexado
e tem o formato
projects/PROJECT_NUMBER/locations/global/memberships/MEMBERSHIP_ID,
em que
PROJECT_NUMBER é o número do projeto host da frota. Especifique
o mesmo número do projeto ao qual seu cluster pertence atualmente
MEMBERSHIP_ID: precisa ser o ID da associação da frota do
cluster atual. Os clusters anexados ao GKE usarão esse valor como
nome do cluster.
[[["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 2024-06-26 UTC."],[],[],null,["# Migrate your CNCF conformant cluster\n\nThe predecessor version of GKE attached clusters is known as GKE attached clusters\n(previous generation). Migrating from the earlier\nversion of GKE attached clusters to the current generation gives you access to this\nfunctionality, including lifecycle management and Fleet registration. Migration\nis a one-way operation: once you have migrated to the current generation of\nGKE attached clusters, there is no way to return to GKE attached clusters (previous generation).\n\nVersion numbering policy\n------------------------\n\nThese documents refer to the GKE attached clusters version as the platform version,\nto distinguish it from the Kubernetes version. GKE attached clusters uses the same\nversion numbering convention as GKE - for example, 1.21.5-gke.1. When attaching\nor updating your cluster, you must choose a platform version whose minor version\nis the same as or one level below the Kubernetes version of your cluster. For\nexample, you can attach a cluster running Kubernetes v1.22.\\* with\nGKE attached clusters platform version 1.21.\\* or 1.22.\\*.\n\nThis lets you upgrade your cluster to the next minor version before upgrading\nGKE attached clusters.\n\nEnsure Workload Identity is enabled\n-----------------------------------\n\nExisting clusters from GKE attached clusters (previous generation) must have Workload\nIdentity enabled before being migrated to the current generation of GKE attached clusters.\n\nTo determine whether WI is enabled, run the following command and check\nthe output for any Workload Identity field: \n\n gcloud container hub memberships describe \u003cvar translate=\"no\"\u003eMEMBERSHIP_NAME\u003c/var\u003e\n\nIf Workload Identity is not enabled, the membership must be updated to enable it.\nThe command to update your cluster's membership varies slightly depending on whether your cluster has a public or private OIDC issuer. Choose the tab that applies to your cluster:\n\n\u003cbr /\u003e\n\n### Private OIDC issuer\n\n gcloud container hub memberships register \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003eMEMBERSHIP_NAME\u003c/span\u003e\u003c/var\u003e \\\n --context=\u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003eKUBECONFIG_CONTEXT\u003c/span\u003e\u003c/var\u003e \\\n --kubeconfig=\u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003eKUBECONFIG_PATH\u003c/span\u003e\u003c/var\u003e \\\n --enable-workload-identity \\\n --has-private-issuer\n\nReplace:\n\n- \u003cvar translate=\"no\"\u003eMEMBERSHIP_NAME\u003c/var\u003e: the membership name of your cluster\n- \u003cvar translate=\"no\"\u003eKUBECONFIG_CONTEXT\u003c/var\u003e: context in the kubeconfig for accessing the AKS cluster\n- \u003cvar translate=\"no\"\u003eKUBECONFIG_PATH\u003c/var\u003e: path to your kubeconfig file\n\n### Public OIDC issuer\n\n- Retrieve your cluster's OIDC issuer URL. Specific instructions vary by distribution.\n\nThe output of this command will be the URL of your OIDC issuer. Save this value\nfor use later.\n\n- Update the membership:\n\n gcloud container fleet memberships register \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003eMEMBERSHIP_NAME\u003c/span\u003e\u003c/var\u003e \\\n --context=\u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003eKUBECONFIG_CONTEXT\u003c/span\u003e\u003c/var\u003e \\\n --kubeconfig=\u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003eKUBECONFIG_PATH\u003c/span\u003e\u003c/var\u003e \\\n --enable-workload-identity \\\n --public-issuer-url=\u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003eOIDC_URL\u003c/span\u003e\u003c/var\u003e\n\nReplace:\n\n- \u003cvar translate=\"no\"\u003eMEMBERSHIP_NAME\u003c/var\u003e: the membership name of your cluster\n- \u003cvar translate=\"no\"\u003eKUBECONFIG_CONTEXT\u003c/var\u003e: context in the kubeconfig for accessing the AKS cluster\n- \u003cvar translate=\"no\"\u003eKUBECONFIG_PATH\u003c/var\u003e: path to your kubeconfig\n- \u003cvar translate=\"no\"\u003eOIDC_URL\u003c/var\u003e: the OIDC URL retrieved earlier\n\nMigrate your cluster\n--------------------\n\nTo migrate your cluster from GKE attached clusters (previous generation) to GKE attached clusters:\n\n1. Extract your cluster's kubeconfig context and store it in the\n KUBECONFIG_CONTEXT environment variable:\n\n KUBECONFIG_CONTEXT=$(kubectl config current-context)\n\n2. Run the following command to migrate your cluster to the current generation\n of GKE attached clusters. This command extracts the relevant details of your cluster's\n configuration and registers your cluster with Google Fleet Management, and\n installs or upgrades any necessary software, such as the lifecycle agent, on\n your cluster.\n\n gcloud container attached clusters import \\\n --location=\u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003eGOOGLE_CLOUD_REGION\u003c/span\u003e\u003c/var\u003e \\\n --fleet-membership=\u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003eFLEET_MEMBERSHIP\u003c/span\u003e\u003c/var\u003e \\\n --platform-version=\u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003ePLATFORM_VERSION\u003c/span\u003e\u003c/var\u003e \\\n --distribution=\u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003eCLUSTER_DISTRIBUTION\u003c/span\u003e\u003c/var\u003e \\\n --context=\u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003eKUBECONFIG_CONTEXT\u003c/span\u003e\u003c/var\u003e \\\n [--kubeconfig=\u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-n\"\u003eKUBECONFIG_PATH\u003c/span\u003e\u003c/var\u003e]\n\n Replace:\n - \u003cvar translate=\"no\"\u003eGOOGLE_CLOUD_REGION\u003c/var\u003e: the Google Cloud location from which your cluster is administered\n - \u003cvar translate=\"no\"\u003eFLEET_MEMBERSHIP\u003c/var\u003e: the fully qualified membership designator of your registered cluster (see below)\n - \u003cvar translate=\"no\"\u003ePLATFORM_VERSION\u003c/var\u003e: the version of GKE attached clusters that you want to migrate to (example: v1.22.0-gke.1)\n - \u003cvar translate=\"no\"\u003eCLUSTER_DISTRIBUTION\u003c/var\u003e: the cluster type - `eks` for AWS's Elastic Kubernetes Service, `aks` for Azure Kubernetes Service, or `generic` for any other distribution\n - \u003cvar translate=\"no\"\u003eKUBECONFIG_CONTEXT\u003c/var\u003e: the name of the context in your `kubeconfig` to connect to your cluster with\n - \u003cvar translate=\"no\"\u003eKUBECONFIG_PATH\u003c/var\u003e: the location of your `kubeconfig` file. If not specified, the default is `~/.kube/config`\n\n The membership designator is a string that uniquely identifies your attached\n cluster and has the form\n `projects/`\u003cvar translate=\"no\"\u003ePROJECT_NUMBER\u003c/var\u003e`/locations/global/memberships/`\u003cvar translate=\"no\"\u003eMEMBERSHIP_ID\u003c/var\u003e,\n where\n - \u003cvar translate=\"no\"\u003ePROJECT_NUMBER\u003c/var\u003e is your Fleet host project number. You must\n specify the same project number as one your cluster currently belongs to\n\n - \u003cvar translate=\"no\"\u003eMEMBERSHIP_ID\u003c/var\u003e: this must be the fleet membership ID of\n your existing cluster. GKE attached clusters will use this value as your\n cluster name."]]
