From e0a2db4f0e5c25339975270345f59d7c22f8100e Mon Sep 17 00:00:00 2001 From: Nico <86240618+nico-shishkin@users.noreply.github.com> Date: Tue, 28 Nov 2023 13:23:38 +0100 Subject: [PATCH] Update k8s.md --- docs/_include/general-shipping/k8s.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/_include/general-shipping/k8s.md b/docs/_include/general-shipping/k8s.md index 5ab509d2..31de34b3 100644 --- a/docs/_include/general-shipping/k8s.md +++ b/docs/_include/general-shipping/k8s.md @@ -59,7 +59,7 @@ logzio-monitoring logzio-helm/logzio-monitoring | `<>` | The cluster's name, to easily identify the telemetry data for each environment. | | `<>` | (*optional*) HTTP/s listener endpoint that receives JSON input, overrides the Logz.io listener. | -### Deployment Events Versioning +### Deployment events versioning In order to add an indication for the versioning in our K8S 360 and Service Overview UI, the following annotation should be added to the metadata of each resource you'd like to track its versioning. Commit URL structure: `https://github.com///commit/` @@ -75,7 +75,7 @@ metadata: For log shipping troubleshooting, see our [user guide](https://docs.logz.io/user-guide/kubernetes-troubleshooting/). -## Send your Metrics +## Send your metrics ```sh helm install -n monitoring \