From 83698e018e53d177a3d14d27c7591b7fc2926f9c Mon Sep 17 00:00:00 2001 From: Mark Chmarny Date: Tue, 9 Jun 2020 15:17:52 -0700 Subject: [PATCH] deployment in stead of run for 1.15+ compatibility Addresses #572 Current instructions for deploying Zipkin do not create service which makes the following command fail because there is no service, as starting with 1.15 k8s no longer creates service under the `run` command. Changing the `run` to `create deployment` ```shell kubectl create deployment zipkin --image openzipkin/zipkin ``` Which creates will allow the following command to create a service and expose its port. ```shell kubectl expose deployment zipkin --type ClusterIP --port 9411 ``` --- howto/diagnose-with-tracing/zipkin.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/howto/diagnose-with-tracing/zipkin.md b/howto/diagnose-with-tracing/zipkin.md index cf4d39d69..490e097c1 100644 --- a/howto/diagnose-with-tracing/zipkin.md +++ b/howto/diagnose-with-tracing/zipkin.md @@ -66,13 +66,13 @@ The following steps shows you how to configure Dapr to send distributed tracing First, deploy Zipkin: ```bash -kubectl run zipkin --image openzipkin/zipkin --port 9411 +kubectl create deployment zipkin --image openzipkin/zipkin ``` Create a Kubernetes service for the Zipkin pod: ```bash -kubectl expose deploy zipkin --type ClusterIP --port 9411 +kubectl expose deployment zipkin --type ClusterIP --port 9411 ``` Next, create the following YAML files locally: @@ -156,4 +156,4 @@ set `samplingRate : "0"` in the configuration. The valid range of samplingRate i ## References -* [How-To: Use W3C Trace Context for distributed tracing](../../howto/use-w3c-tracecontext/readme.md) \ No newline at end of file +* [How-To: Use W3C Trace Context for distributed tracing](../../howto/use-w3c-tracecontext/readme.md)