From e41586e684c22f77e08f478a57d1748e57cd535e Mon Sep 17 00:00:00 2001 From: sundar-cs <58211779+sundar-cs@users.noreply.github.com> Date: Tue, 11 Aug 2020 20:21:42 +0530 Subject: [PATCH] Added Docker interactive flag for generate manifests command (#1154) Signed-off-by: sundar --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 06edb87f1..eef060486 100644 --- a/README.md +++ b/README.md @@ -54,7 +54,7 @@ The official documentation for the Jaeger Operator, including all its customizat Sometimes it is preferable to generate plain manifests files instead of running an operator in a cluster. `jaeger-operator generate` generates kubernetes manifests from a given CR. In this example we apply the manifest generated by [examples/simplest.yaml](https://raw.githubusercontent.com/jaegertracing/jaeger-operator/master/deploy/examples/simplest.yaml) to the namespace `jaeger-test`: ```bash -curl https://raw.githubusercontent.com/jaegertracing/jaeger-operator/master/deploy/examples/simplest.yaml | docker run --rm jaegertracing/jaeger-operator:master generate | kubectl apply -n jaeger-test -f - +curl https://raw.githubusercontent.com/jaegertracing/jaeger-operator/master/deploy/examples/simplest.yaml | docker run -i --rm jaegertracing/jaeger-operator:master generate | kubectl apply -n jaeger-test -f - ``` It is recommended to deploy the operator instead of generating a static manifest.