To finalize the upgrade of your cluster and complete the migration to the Knative serving fleet component, you must remove all the stale and unused resources from your cluster.
Before you begin
You must first review and ensure that you meet the requirements for upgrading.
The commands on this page use the environment variables and migration script from the upgrade preparation step.
It is important that you perform each step of this process in the specified order.
Overview
In this step, the migration script is used to perform the following:
- Enforce full control of your Knative serving resources by the
the
appdevexperience-operatoroperator. - Delete the bundle Istio and Knative serving GKE add-on.
- Delete all helper configmaps.
You can then re-enable the "scaling to zero" feature.
Complete the Knative serving upgrade
To complete your Knative serving upgrade and finalize the migration process:
Run the following command to start the migration script:
./migration-addon.sh --command finalizeIn the terminal, the migration script prompts you to confirm that you want to proceed. Enter
yto finalize the process.The prompts during the process this final step look similar to the following:
In the process of cleaning up, the script performs the following: 1. enforcing Knative serving operator fully controls Knative serving resources.<br> 2. deleting Istio slim installed by Knative serving GKE add-on<br> 3. deleting helper configmaps Continue? [Y/n] y<br> 1. enforcing Knative serving operator fully controls Knative serving resources. cloudrun.operator.run.cloud.google.com/cloud-run patched Waiting for Knative serving serving to be ready... Knative serving serving is ready. 2. Deleting Istio slim resources 3. Deleting helper configmaps Cleanup is done. The upgrade to new Knative serving completes! <br>Run the following command to enable "scaling to 0":
kubectl patch cm config-autoscaler -n knative-serving -p '{"data":{"enable-scale-to-zero": "true"}}'