From 210d8fb94eaa0e0b5c890d22694a9cb2dadfb83c Mon Sep 17 00:00:00 2001 From: Sabin Thomas <thomasmsabin@gmail.com> Date: Wed, 31 Jan 2018 16:59:11 -0500 Subject: [PATCH] Update minikube docs to reference jaeger manifests instead of non-existent zipkin manifest --- deployment/kubernetes-minikube.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/deployment/kubernetes-minikube.md b/deployment/kubernetes-minikube.md index f4c50cd..9756019 100644 --- a/deployment/kubernetes-minikube.md +++ b/deployment/kubernetes-minikube.md @@ -66,7 +66,7 @@ kubectl create -f deploy/kubernetes/manifests/sock-shop-ns.yaml -f deploy/kubern To start Opentracing run the following command after deploying the sock shop ``` -kubectl apply -f deploy/kubernetes/manifests-zipkin/zipkin-ns.yaml -f deploy/kubernetes/manifests-zipkin +kubectl create -f deploy/kubernetes/manifests-jaeger/jaeger.yaml -f deploy/kubernetes/manifests-jaeger ``` Wait for all the Sock Shop services to start: @@ -81,8 +81,8 @@ Once the application is deployed, navigate to http://192.168.99.100:30001 to see ### Opentracing -Zipkin is part of the deployment and has been written into some of the services. While the system is up you can view the traces in -Zipkin at http://192.168.99.100:30002. Currently orders provide the most comprehensive traces, but this requires a user to place an order. +Jaegar is part of the deployment and has been written into some of the services. While the system is up you can view the traces in +Jaegar at http://192.168.99.100:30552. Currently orders provide the most comprehensive traces, but this requires a user to place an order. ### Run tests