Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Versi pendahulunya dari cluster terpasang GKE dikenal sebagai cluster terpasang GKE (generasi sebelumnya). Dengan bermigrasi dari versi cluster terlampir GKE sebelumnya ke generasi saat ini, Anda akan mendapatkan akses ke fungsi ini, termasuk pengelolaan siklus proses dan pendaftaran Fleet. Migrasi adalah operasi satu arah: setelah Anda bermigrasi ke generasi saat ini dari cluster terlampir GKE, tidak ada cara untuk kembali ke cluster terlampir GKE (generasi sebelumnya).
Kebijakan penomoran versi
Dokumen ini menyebut versi cluster terlampir GKE sebagai versi platform, untuk membedakannya dengan versi Kubernetes. Cluster terlampir GKE menggunakan konvensi penomoran versi yang sama dengan GKE - misalnya, 1.21.5-gke.1. Saat melampirkan
atau mengupdate cluster, Anda harus memilih versi platform yang versi minornya
sama dengan atau satu tingkat di bawah versi Kubernetes cluster Anda. Misalnya, Anda dapat melampirkan cluster yang menjalankan Kubernetes v1.22.* dengan versi platform cluster terlampir GKE 1.21.* atau 1.22.*.
Dengan begitu, Anda dapat mengupgrade cluster ke versi minor berikutnya sebelum mengupgrade cluster terlampir GKE.
Pastikan Workload Identity diaktifkan
Cluster yang ada dari cluster terpasang GKE (generasi sebelumnya) harus mengaktifkan Workload Identity sebelum dimigrasikan ke cluster terpasang GKE generasi saat ini.
Untuk menentukan apakah WI diaktifkan, jalankan perintah berikut dan periksa output untuk mengetahui apakah ada kolom Workload Identity:
Jalankan perintah berikut untuk memigrasikan cluster Anda ke generasi saat ini dari cluster terlampir GKE. Perintah ini mengekstrak detail yang relevan dari konfigurasi
cluster Anda dan mendaftarkan cluster Anda ke Google Fleet Management, serta
menginstal atau mengupgrade software yang diperlukan, seperti agen siklus proses, di
cluster Anda.
GOOGLE_CLOUD_REGION: Google Cloud lokasi
tempat cluster Anda dikelola
FLEET_MEMBERSHIP: penentu keanggotaan yang sepenuhnya memenuhi syarat
dari cluster terdaftar Anda (lihat di bawah)
PLATFORM_VERSION: versi cluster terlampir GKE yang ingin Anda migrasikan (contoh: v1.22.0-gke.1)
CLUSTER_DISTRIBUTION: jenis cluster - eks untuk
Elastic Kubernetes Service AWS, aks untuk Azure Kubernetes Service, atau
generic untuk distribusi lainnya
KUBECONFIG_CONTEXT: nama konteks di
kubeconfig untuk terhubung ke cluster Anda
KUBECONFIG_PATH: lokasi file kubeconfig Anda.
Jika tidak ditentukan, defaultnya adalah ~/.kube/config
Penentu keanggotaan adalah string yang secara unik mengidentifikasi cluster terlampir Anda dan memiliki bentuk
projects/PROJECT_NUMBER/locations/global/memberships/MEMBERSHIP_ID,
dengan
PROJECT_NUMBER adalah nomor project host Fleet Anda. Anda harus
menentukan nomor project yang sama dengan nomor project tempat cluster Anda saat ini berada
MEMBERSHIP_ID: ini harus berupa ID keanggotaan fleet dari
cluster yang ada. Cluster terlampir GKE akan menggunakan nilai ini sebagai nama cluster Anda.
[[["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-07-31 UTC."],[],[],null,["# Migrate your EKS attached 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.\n\n1. Retrieve your cluster's OIDC issuer URL with the following command:\n\n aws eks describe-cluster \\\n --region \u003cvar translate=\"no\"\u003eAWS_REGION\u003c/var\u003e \\\n --name \u003cvar translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e \\\n --query \"cluster.identity.oidc.issuer\" \\\n --output text\n\n The output of this command will be the URL of your OIDC issuer. Save this value\n for use later.\n2. Update the membership:\n\n gcloud container fleet memberships register \u003cvar translate=\"no\"\u003eMEMBERSHIP_NAME\u003c/var\u003e \\\n --context=\u003cvar translate=\"no\"\u003eKUBECONFIG_CONTEXT\u003c/var\u003e \\\n --kubeconfig=\u003cvar translate=\"no\"\u003eKUBECONFIG_PATH\u003c/var\u003e \\\n --enable-workload-identity \\\n --public-issuer-url=\u003cvar translate=\"no\"\u003eOIDC_URL\u003c/var\u003e\n\n Replace:\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 EKS cluster\n - \u003cvar translate=\"no\"\u003eKUBECONFIG_PATH\u003c/var\u003e: path to your kubeconfig file\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."]]
