For Cloud Run for Anthos, you need to evaluate new code with a subset of production traffic before full rollout. What deployment approach enables traffic sampling between versions?

Cloud Run for Anthos natively supports traffic splitting between different revisions of a service. When you deploy a new version, it creates a new revision. You can then configure the service to direct a specific percentage of incoming traffic to this new revision, while the remaining traffic goes to the previous stable revision. This allows for controlled rollout and testing with a subset of production traffic. Deploying a new service and using Cloud Load Balancing is overly complex for this scenario, as Cloud Run handles traffic management internally. Cloud Build triggers manage deployments, but traffic splitting is configured on the Cloud Run service itself, not directly within the build trigger. Traffic Director is used for service mesh capabilities with GKE, not for direct traffic management within Cloud Run for Anthos services.