Jika nilai klien Kf dan server Kf tidak cocok, tetapi versi servernya adalah v2.10.x, instal CLI Kf v2.11.28 sebelum melanjutkan.
Jika nilai server Kf lebih lama dari v2.10.x, Anda harus mengupgrade secara bertahap ke Kf v2.10.x terlebih dahulu untuk melanjutkan.
Pastikan Kf berfungsi dengan baik sebelum mengupgrade
Jalankan kf doctor untuk memeriksa status cluster Anda. Pastikan semua pengujian lulus
sebelum Anda melanjutkan.
$ kf doctor
...
=== RUN doctor/user
=== RUN doctor/user/ContainerRegistry
--- PASS: doctor/user
--- PASS: doctor/user/ContainerRegistry
...
Jika Anda melihat pesan FAIL atau Error: environment failed checks, ikuti
panduan dalam output kf doctor, atau lihat panduan pemecahan masalah untuk menyelesaikan masalah dan coba lagi perintah tersebut
hingga berhasil.
Jalankan doctor untuk memastikan versi yang baru diinstal berfungsi dengan baik:
kfdoctor--retries=20
Perintah ini menjalankan pemeriksaan cluster beberapa kali. Wajar jika beberapa
upaya gagal saat pengontrol baru dimulai.
Jika perintah gagal dengan pesan Error: environment failed checks,
ikuti panduan dalam output doctor untuk menyelesaikan masalah dan coba lagi
perintah hingga berhasil.
Jika langkah-langkah verifikasi berhasil, cluster Anda telah berhasil diupgrade. Jika Anda mengalami masalah, tinjau halaman dukungan untuk mendapatkan panduan.
[[["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-04 UTC."],[],[],null,["This document describes how to upgrade an existing Kf installation and its dependencies.\n\n\u003cbr /\u003e\n\nAs part of the upgrade procedure, ensure that your Kf\ninstallation uses the latest version of the Kf operator:\n\n- Confirm your current Kf version can upgrade to Kf v2.11.28.\n- Upgrade to Kf v2.11.28.\n- Upgrade dependencies (if needed).\n\nBefore you begin **Warning:** The steps on this page are for upgrading Kf v2.10.x (or Kf v2.8.x) to Kf v2.11.28. If your current version is not Kf v2.10.x, you must first upgrade incrementally until your current version is v2.10.x (one minor version at a time). (For upgrading from v2.8.x on GKE clusters, please pay close attention to the 'Upgrade/Install Config Connector' part.)\n\nYou will need:\n\n- An existing cluster with Kf installed.\n- Access to a machine with `gcloud`, `kf`, and `kubectl` installed.\n\nPrepare for the upgrade\n\nConnect to your target cluster \n\n gcloud container clusters get-credentials \u003cvar translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e \\\n --zone \u003cvar translate=\"no\"\u003eCLUSTER_ZONE\u003c/var\u003e \\\n --project \u003cvar translate=\"no\"\u003eCLUSTER_PROJECT_ID\u003c/var\u003e\n\nConfirm that your current Kf CLI and server versions match\n\nRun `kf debug` and validate the Kf CLI and\nKf server versions match.\n\n- The CLI version is listed under `Kf Client`.\n- The Kf server version is listed under `kf[\"app.kubernetes.io/version\"]`.\n\n $ kf debug\n ...\n Version:\n Kf Client: v2.11.27\n Server version: v1.31.1-gke.2105000\n kf\\[\"app.kubernetes.io/version\"\\]: v2.11.27\n ...\n\nIf the Kf client and Kf server\nvalues **do not** match, but the server version is v2.10.x, [install](#upgrade-the-cli) the Kf v2.11.28 CLI before you continue.\n\nIf the Kf server value is older than v2.10.x, you must first incrementally upgrade to Kf v2.10.x to continue.\n\nConfirm that Kf is healthy before upgrading\n\nRun `kf doctor` to check the state of your cluster. Ensure all tests pass\nbefore you continue. \n\n $ kf doctor\n ...\n === RUN doctor/user\n === RUN doctor/user/ContainerRegistry\n --- PASS: doctor/user\n --- PASS: doctor/user/ContainerRegistry\n ...\n\nIf you see any `FAIL` or `Error: environment failed checks` messages, follow the\nguidance in the `kf doctor` output, or view the [troubleshooting guide](/migrate/kf/docs/2.11/support/troubleshooting) to resolve the issue and retry the command\nuntil it is successful.\n\nUpgrade the operator\n\nThe Kf operator performs upgrades for you.\n\n1. Apply the operator yaml:\n\n **Note:** This operation starts immediately, and is not reversible. \n\n ```\n kubectl apply -f \"https://storage.googleapis.com/kf-releases/v2.11.28/operator.yaml\"\n ```\n\nUpgrade Kf dependencies\n\n1. Upgrade Tekton:\n\n\n ```\n kubectl apply -f \"https://storage.googleapis.com/tekton-releases/pipeline/previous/v0.68.0/release.yaml\"\n ```\n\n \u003cbr /\u003e\n\n2. Upgrade to Cloud Service Mesh v1.23.3-asm.1+config1:\n\n 1. Follow the steps in the [Cloud Service Mesh upgrade guide](/service-mesh/v1.11/docs/unified-install/upgrade).\n\n\u003c!-- --\u003e\n\n1. Upgrade/Install Config Connector:\n\n For upgrading from Kf v2.11:\n Please follow the steps in the 'Install Config Connector' step in [Kf Install](/migrate/kf/docs/2.11/install)\n\n For upgrading from Kf v2.7:\n 1. [Download](https://storage.googleapis.com/configconnector-operator/1.129.2/release-bundle.tar.gz) the required Config Connector Operator tar file.\n\n | **Note:** Keep a copy of the installation bundle as you need this bundle to uninstall Config Connector.\n 2. Extract the tar file.\n\n tar zxvf release-bundle.tar.gz\n\n 3. Install the Config Connector operator on your cluster.\n\n kubectl apply -f operator-system/configconnector-operator.yaml\n\n \u003cbr /\u003e\n\nUpgrade to the Kf v2.11.28 CLI\n\n1. Install the CLI:\n\n Linux\n\n This command installs the Kf CLI for all users on the system. Follow the\n instructions in the Cloud Shell tab to install it just for yourself. \n\n gcloud storage cp gs://kf-releases/v2.11.28/kf-linux /tmp/kf\n chmod a+x /tmp/kf\n sudo mv /tmp/kf /usr/local/bin/kf\n\n Mac\n\n This command installs `kf` for all users on the system. \n\n gcloud storage cp gs://kf-releases/v2.11.28/kf-darwin /tmp/kf\n chmod a+x /tmp/kf\n sudo mv /tmp/kf /usr/local/bin/kf\n\n Cloud Shell\n\n This command installs `kf` on your Cloud Shell instance if you use `bash`,\n the instructions may need to be modified for other shells. \n\n mkdir -p ~/bin\n gcloud storage cp gs://kf-releases/v2.11.28/kf-linux ~/bin/kf\n chmod a+x ~/bin/kf\n echo \"export PATH=$HOME/bin:$PATH\" \u003e\u003e ~/.bashrc\n source ~/.bashrc\n\n Windows\n\n This downloads `kf` to current directory. Add it to the path if you\n want to call if from anywhere other than the current directory. \n\n gcloud storage cp gs://kf-releases/v2.11.28/kf-windows.exe kf.exe\n\n2. Validate the Kf CLI and\n Kf server versions match:\n\n - The CLI version is listed under `Kf Client`.\n - The Kf server version is listed under `kf[\"app.kubernetes.io/version\"]`.\n\n $ kf debug\n ...\n Version:\n Kf Client: v2.11.28\n Server version: v1.31.1-gke.2105000\n kf\\[\"app.kubernetes.io/version\"\\]: v2.11.28\n ...\n\nVerify that Kf upgraded successfully\n\n1. Run `doctor` to ensure the newly installed version is healthy:\n\n kf doctor --retries=20\n\n The command runs cluster checks several times. It's normal for a few of\n the attempts to fail while the new controllers are starting.\n\n If the command fails with the message `Error: environment failed checks`,\n follow the guidance in the `doctor` output to resolve the issue and retry the\n command until it is successful.\n\nIf the verification steps pass, your cluster has successfully been upgraded! If you have any issues, please review the [support](/migrate/kf/docs/2.11/support) page for guidance."]]
