From 0758c9afe5ce4b527a311dfd99ccf71ef4a92778 Mon Sep 17 00:00:00 2001 From: Andrey Blazejuk Date: Sat, 18 Oct 2025 06:23:22 -0300 Subject: [PATCH] Refactor headings in installation.md for clarity Updated headings for consistency in installation documentation. Signed-off-by: Andrey Blazejuk --- website/docs/getting-started/installation.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/website/docs/getting-started/installation.md b/website/docs/getting-started/installation.md index ab53892d..1d1f3f44 100644 --- a/website/docs/getting-started/installation.md +++ b/website/docs/getting-started/installation.md @@ -114,11 +114,11 @@ Visit https://docs.litmuschaos.io to find more info. > **Note:** Litmus uses Kubernetes CRDs to define chaos intent. Helm3 handles CRDs better than Helm2. Before you start running a chaos experiment, verify if Litmus is installed correctly. -## **Install Litmus using kubectl** +## Install Litmus using kubectl In this method the users need to install mongo first via helm and then apply the installation manifest. Follow the instructions [here](https://github.com/litmuschaos/litmus/tree/master/chaoscenter#installation-steps-for-litmus-300-beta9). -### **Install mongo** +### Install mongo ```bash helm repo add bitnami https://charts.bitnami.com/bitnami @@ -172,9 +172,9 @@ For advanced installation visit [here](../user-guides/chaoscenter-advanced-insta --- -## **Verify your installation** +## Verify your installation -#### **Verify if the frontend, server, and database pods are running** +#### Verify if the frontend, server, and database pods are running - Check the pods in the namespace where you installed Litmus: @@ -217,7 +217,7 @@ For advanced installation visit [here](../user-guides/chaoscenter-advanced-insta --- -## **Accessing the ChaosCenter** +## Accessing the ChaosCenter To setup and login to ChaosCenter expand the available services just created and copy the `PORT` of the `litmusportal-frontend-service` service