Skip to content

Commit e187158

Browse files
authored
Clarifying comments (#187)
1 parent 6efc12c commit e187158

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

docs/canary_ab_deployment.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,8 @@ Having the Istio installed, figure out the Istio gateway endpoint on your K8s cl
1616
GATEWAY_IP=$(kubectl get svc istio-ingressgateway -n istio-system -o jsonpath='{.status.loadBalancer.ingress[0].ip}')
1717
```
1818

19+
You don't need to create any Istio resources (e.g. Gateway or VirtualService) at this point. It will be handled by the AzDo pipeline that builds and deploys a scoring image.
20+
1921
#### 2. Set up variables
2022

2123
There are some extra variables that you need to setup in ***devopsforai-aml-vg*** variable group (see [getting started](./getting_started.md)):
@@ -35,7 +37,7 @@ The result of the pipeline will be a registered Docker image in the ACR reposito
3537

3638
![scoring image](./images/scoring_image.png)
3739

38-
The pipeline will also deploy the scoring image to the Kubernetes cluster.
40+
The pipeline creates Istio Gateway and VirtualService and deploys the scoring image to the Kubernetes cluster.
3941

4042
```bash
4143
kubectl get deployments --namespace abtesting

0 commit comments

Comments
 (0)