From 806b233d58be0655efb2252dbda38d753803b0d5 Mon Sep 17 00:00:00 2001
From: stefanprodan <stefan.prodan@gmail.com>
Date: Tue, 18 Jun 2019 13:22:18 +0300
Subject: [PATCH] Fix typo in ClusterIP FAQ

---
 docs/gitbook/faq.md | 37 ++++++++++++++++++++++++++++++++++---
 1 file changed, 34 insertions(+), 3 deletions(-)

diff --git a/docs/gitbook/faq.md b/docs/gitbook/faq.md
index ebf5b284..354da08b 100644
--- a/docs/gitbook/faq.md
+++ b/docs/gitbook/faq.md
@@ -79,9 +79,12 @@ spec:
 
 Based on the canary spec service, Flagger generates the following Kubernetes ClusterIP service:
 
-* `<name>.<namespaces>.vc.cluster.local` with selector `app=<name>-primary`
-* `<name>-primary.<namespaces>.vc.cluster.local` with selector `app=<name>-primary`
-* `<name>-canary.<namespaces>.vc.cluster.local` with selector `app=<name>`
+* `<targetRef.name>.<namespace>.svc.cluster.local`  
+    selector `app=<name>-primary`
+* `<targetRef.name>-primary.<namespace>.svc.cluster.local`  
+    selector `app=<name>-primary`
+* `<targetRef.name>-canary.<namespace>.svc.cluster.local`  
+    selector `app=<name>`
 
 This ensures that traffic coming from a namespace outside the mesh to `podinfo.test:9898`
 will be routed to the latest stable release of your app. 
@@ -101,6 +104,34 @@ spec:
     port: 9898
     protocol: TCP
     targetPort: http
+---
+apiVersion: v1
+kind: Service
+metadata:
+  name: podinfo-primary
+spec:
+  type: ClusterIP
+  selector:
+    app: podinfo-primary
+  ports:
+  - name: http
+    port: 9898
+    protocol: TCP
+    targetPort: http
+---
+apiVersion: v1
+kind: Service
+metadata:
+  name: podinfo-canary
+spec:
+  type: ClusterIP
+  selector:
+    app: podinfo
+  ports:
+  - name: http
+    port: 9898
+    protocol: TCP
+    targetPort: http
 ```
 
 The `podinfo-canary.test:9898` address is available only during the