From 2da8b7290e6b9c98e34e3e46414c7452dee4a156 Mon Sep 17 00:00:00 2001
From: Albert <26584478+albertteoh@users.noreply.github.com>
Date: Wed, 7 Dec 2022 16:29:17 +1100
Subject: [PATCH] Update Cloud Native Deployment section of README (#4076)

---
 README.md | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 7403e16bfa4..efe77936781 100644
--- a/README.md
+++ b/README.md
@@ -96,9 +96,14 @@ traces with tens of thousands of spans (e.g. we tried a trace with 80,000 spans)
 ### Cloud Native Deployment
 
 Jaeger backend is distributed as a collection of Docker images. The binaries support various configuration methods,
-including command line options, environment variables, and configuration files in multiple formats (yaml, toml, etc.)
-Deployment to Kubernetes clusters is assisted by [Kubernetes templates](https://github.com/jaegertracing/jaeger-kubernetes)
-and a [Helm chart](https://github.com/jaegertracing/helm-charts).
+including command line options, environment variables, and configuration files in multiple formats (yaml, toml, etc.).
+
+The recommended way to deploy Jaeger in a production Kubernetes cluster is via the [Jaeger Operator](https://github.com/jaegertracing/jaeger-operator).
+
+The Jaeger Operator provides a [CLI to generate](https://github.com/jaegertracing/jaeger-operator#experimental-generate-kubernetes-manifest-file) Kubernetes manifests from the Jaeger CR.
+This can be considered as an alternative source over plain Kubernetes manifest files.
+
+The Jaeger ecosystem also provides a [Helm chart](https://github.com/jaegertracing/helm-charts) as an alternative way to deploy Jaeger.
 
 ### Observability