From 9ef3e562d2a598ffa9efa44dd9b7435171138134 Mon Sep 17 00:00:00 2001 From: Milvus-doc-bot Date: Mon, 23 Dec 2024 12:32:38 +0000 Subject: [PATCH] Release new docs to master --- v2.5.x/site/en/adminGuide/config_jaeger_tracing.md | 2 +- version.json | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/v2.5.x/site/en/adminGuide/config_jaeger_tracing.md b/v2.5.x/site/en/adminGuide/config_jaeger_tracing.md index f19d750e9..13fed254c 100644 --- a/v2.5.x/site/en/adminGuide/config_jaeger_tracing.md +++ b/v2.5.x/site/en/adminGuide/config_jaeger_tracing.md @@ -36,7 +36,7 @@ NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE jaeger-operator 1 1 1 1 48s ``` -### 2. Deploy Jager +### 2. Deploy Jaeger The simplest possible way to create a Jaeger instance is by creating a YAML file like the following example. This will install the default AllInOne strategy, which deploys the **all-in-one** image (combining **jaeger-agent**, **jaeger-collector**, **jaeger-query**, and Jaeger UI) in a single pod, using **in-memory storage** by default. diff --git a/version.json b/version.json index 8085d97f0..afcd7732d 100644 --- a/version.json +++ b/version.json @@ -1,4 +1,4 @@ { - "version": "v2.4.x", + "version": "v2.5.x", "released": "yes" }