Traffic splitting distributes requests between application versions by assigning percentages to service revisions. It supports canary releases by running stable and new versions side by side, then increasing the new version’s share as confidence grows. section 8.2.2 section 8.1.1
A Knative rollout typically follows these steps:
- Start with 100% of traffic routed to the latest revision by default. section 8.2.2
- Edit the Knative Service’s spec.traffic rules to assign percentages to stable and new revisions. section 8.2.2
- Send requests with curl to confirm that both revisions are serving responses. section 8.2.2
- Increase the new revision’s percentage after validation, or return 100% to the stable revision when problems appear. section 8.2.2
- Keep all revision percentages totaling 100%; Knative can manage multiple revisions and scale the required ones. section 8.2.2
Splitting notifications-service traffic
Assign 50% of requests to notifications-service-00001 and 50% to the latest revision. Repeated curl requests return either version 1.0.0 or the improved version 1.1.0, allowing the new implementation to be checked before moving all traffic.
