From 0e8ea9e8f41e2e63438d207cc449aba46187a148 Mon Sep 17 00:00:00 2001 From: Daniel Del Rio Date: Fri, 24 Feb 2023 16:48:39 +0100 Subject: [PATCH] Update documentation on service creation Signed-off-by: Daniel Del Rio --- docs/features/experiment.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/features/experiment.md b/docs/features/experiment.md index 6740895d68..b282f3b18b 100644 --- a/docs/features/experiment.md +++ b/docs/features/experiment.md @@ -6,7 +6,7 @@ The Experiment CRD allows users to have ephemeral runs of one or more ReplicaSet running ephemeral ReplicaSets, the Experiment CRD can launch AnalysisRuns alongside the ReplicaSets. Generally, those AnalysisRun is used to confirm that new ReplicaSets are running as expected. -A Service routing traffic to the Experiment ReplicaSet is also generated. +A Service routing traffic to the Experiment ReplicaSet is also generated if a weight for that experiment is set. ## Use cases of Experiments @@ -245,7 +245,7 @@ to `experiment-baseline`, leaving the remaining 90% of traffic to the old stack. !!! note When a weighted experiment step with traffic routing is used, a - Service is auto-created for each experiment template. The traffic routers use + service is auto-created for each experiment template. The traffic routers use this service to send traffic to the experiment pods. By default, the generated Service has the name of the ReplicaSet and inherits