This is a cache of https://docs.openshift.com/serverless/1.33/knative-serving/traffic-splitting/traffic-splitting-using-cli.html. It is a snapshot of the page at 2024-11-24T16:39:06.009+0000.
Traffic splitting using the <strong>cli</strong> - Traffic splitting | Serving | Red Hat OpenShift Serverless 1.33
    OpenShift docs are moving and will soon only be available at docs.redhat.com, the home of all Red Hat product documentation. Explore the new docs experience today.
  1. Documentation
    2. history bug_report picture_as_pdf
×

Traffic splitting using the Knative cli

Using the Knative (kn) cli to create traffic splits provides a more streamlined and intuitive user interface over modifying YAML files directly. You can use the kn service update command to split traffic between revisions of a service.

Creating a traffic split by using the Knative cli

Prerequisites

  • The OpenShift Serverless Operator and Knative Serving are installed on your cluster.

  • You have installed the Knative (kn) cli.

  • You have created a Knative service.

Procedure

  • Specify the revision of your service and what percentage of traffic you want to route to it by using the --traffic tag with a standard kn service update command:

    Example command
    $ kn service update <service_name> --traffic <revision>=<percentage>

    Where:

    • <service_name> is the name of the Knative service that you are configuring traffic routing for.

    • <revision> is the revision that you want to configure to receive a percentage of traffic. You can either specify the name of the revision, or a tag that you assigned to the revision by using the --tag flag.

    • <percentage> is the percentage of traffic that you want to send to the specified revision.

  • Optional: The --traffic flag can be specified multiple times in one command. For example, if you have a revision tagged as @latest and a revision named stable, you can specify the percentage of traffic that you want to split to each revision as follows:

    Example command
    $ kn service update showcase --traffic @latest=20,stable=80

    If you have multiple revisions and do not specify the percentage of traffic that should be split to the last revision, the --traffic flag can calculate this automatically. For example, if you have a third revision named example, and you use the following command:

    Example command
    $ kn service update showcase --traffic @latest=10,stable=60

    The remaining 30% of traffic is split to the example revision, even though it was not specified.