OpenShift Container Platform 4.5 Applications $ oc set route-backends ab-example ab-example-a=198 ab-example-b=2 This means 99% of traffic is sent to service  ab-example-a  and 1% to service  ab-example-b . This command does not scale the deployment. You might be required to do so to have enough pods to handle the request load. $ oc set route-backends ab-example 2. Run the command with no flags to verify the current configuration: 3. To alter the weight of an individual service relative to itself or to the primary service, use the  -- adjust  flag. Specifying a percentage adjusts the service relative to either the primary or the first alternate (if you specify the primary). If there are other backends, their weights are kept proportional to the changed. The following example alters the weight of  ab-example-a  and  ab-example-b  services: $ oc set route-backends ab-example --adjust ab-example-a=200 ab-example-b=10 Alternatively, alter the weight of a service by specifying a percentage: $ oc set route-backends ab-example --adjust ab-example-b=5% By specifying  +  before the percentage declaration, you can adjust a weighting relative to the current setting. For example: $ oc set route-backends ab-example --adjust ab-example-b=+15% The  --equal  flag sets the  weight  of all services to  100 : $ oc set route-backends ab-example --equal The  --zero  flag sets the  weight  of all services to  0 . All requests then return with a 503 error. Not all routers may support multiple or weighted backends. NOTE Procedure 3.4.5.1.4. One service, multiple  DeploymentConfig  objects Example output 1. Create a new application, adding a label  ab-example=true  that will be common to all shards: 72 NAME KIND TO WEIGHT routes/ab-example Service ab-example-a 198 (99%) routes/ab-example Service ab-example-b 2 (1%)