Core service names match deployer names

trisberg · Jan 3, 2020 · 3a4b936 · 3a4b936
1 parent 6f4be3a
commit 3a4b936
Show file tree

Hide file tree

Showing 4 changed files with 13 additions and 14 deletions.
diff --git a/docs/v0.5/getting-started/docker-for-mac.md b/docs/v0.5/getting-started/docker-for-mac.md
@@ -227,16 +227,16 @@ After the deployer is created, you can see the service name by listing deployers
 riff core deployers list
 ```
 ```
-NAME         TYPE       REF      SERVICE               STATUS   AGE
-k8s-square   function   square   k8s-square-deployer   Ready    16s
+NAME         TYPE       REF      URL                                           STATUS   AGE
+k8s-square   function   square   http://k8s-square.default.svc.cluster.local   Ready    35s
 ```
 
 ### invoke the function
 
 In a separate terminal, start port-forwarding to the ClusterIP service created by the deployer.
 
 ```sh
-kubectl port-forward service/k8s-square-deployer 8080:80
+kubectl port-forward service/k8s-square 8080:80
 ```
 ```
 Forwarding from 127.0.0.1:8080 -> 8080

diff --git a/docs/v0.5/getting-started/docker-for-windows.md b/docs/v0.5/getting-started/docker-for-windows.md
@@ -265,20 +265,19 @@ riff core deployer create k8s-square --function-ref square --tail
 After the deployer is created, you can see the service name by listing deployers.
 
 ```sh
-riff core deployer list
+riff core deployers list
 ```
-
 ```
-NAME         TYPE       REF      SERVICE               STATUS   AGE
-k8s-square   function   square   k8s-square-deployer   Ready    21s
+NAME         TYPE       REF      URL                                           STATUS   AGE
+k8s-square   function   square   http://k8s-square.default.svc.cluster.local   Ready    35s
 ```
 
 ### invoke the function
 
 In a separate terminal, start port-forwarding to the ClusterIP service created by the deployer.
 
 ```sh
-kubectl port-forward service/k8s-square-deployer 8080:80
+kubectl port-forward service/k8s-square 8080:80
 ```
 ```
 Forwarding from 127.0.0.1:8080 -> 8080

diff --git a/docs/v0.5/getting-started/gke.md b/docs/v0.5/getting-started/gke.md
@@ -328,16 +328,16 @@ After the deployer is created, you can see the service name by listing deployers
 riff core deployers list
 ```
 ```
-NAME         TYPE       REF      SERVICE               STATUS   AGE
-k8s-square   function   square   k8s-square-deployer   Ready    37s
+NAME         TYPE       REF      URL                                           STATUS   AGE
+k8s-square   function   square   http://k8s-square.default.svc.cluster.local   Ready    35s
 ```
 
 ### invoke the function
 
 In a separate terminal, start port-forwarding to the ClusterIP service created by the deployer.
 
 ```sh
-kubectl port-forward service/k8s-square-deployer 8080:80
+kubectl port-forward service/k8s-square 8080:80
 ```
 ```
 Forwarding from 127.0.0.1:8080 -> 8080

diff --git a/docs/v0.5/getting-started/minikube.md b/docs/v0.5/getting-started/minikube.md
@@ -245,16 +245,16 @@ After the deployer is created, you can see the service name by listing deployers
 riff core deployers list
 ```
 ```
-NAME         TYPE       REF      SERVICE               STATUS   AGE
-k8s-square   function   square   k8s-square-deployer   Ready    7s
+NAME         TYPE       REF      URL                                           STATUS   AGE
+k8s-square   function   square   http://k8s-square.default.svc.cluster.local   Ready    35s
 ```
 
 ### invoke the function
 
 In a separate terminal, start port-forwarding to the ClusterIP service created by the deployer.
 
 ```sh
-kubectl port-forward service/k8s-square-deployer 8080:80
+kubectl port-forward service/k8s-square 8080:80
 ```
 ```
 Forwarding from 127.0.0.1:8080 -> 8080