The Configuration object is updated each time the Knative Service is updated. After the Configuration object is updated, a unique revision is created. The revision mechanism in Knative simplifies multi-version management and enables canary releases. For example, Knative handles traffic distribution among different revisions. You can allocate specific traffic percentages to each revision through the console. If you want to roll back to a previous version after deploying a new one, you can incrementally redirect traffic to the older version to complete the rollback.
Prerequisites
A Knative Service has been deployed in your cluster. For more information, see Quickly deploy a Knative application.
Create a revision
Log on to the ACK console. In the left-side navigation pane, click Clusters.
On the Clusters page, find the cluster that you want to manage and click its name. In the left-side navigation pane, choose .
On the Services tab, select the namespace to which the Knative Service belongs and click the name of the Service. In the upper-right corner of the details page, click Create Revision.
In the Basic Information step, configure the parameters and click Next.
For more information about the parameters, see Configure revision parameters.
In the Traffic Splitting Settings step, configure Revisions and Percent % and click Create.
Revisions: A revision is created each time a Knative Service is updated.
Percent %: The percentage of traffic that is forwarded to a revision. The sum of the traffic percentage values specified for all revisions must be 100%.
You can view and delete revisions on the Revision Information tab of the details page of the Knative Service.
References
You can perform a canary release based on specific traffic percentages for a Knative Service. For more information, see Deploy a canary release for a Knative Service.