5.3.3 release of chart (#8)

* up description up chart version Signed-off-by: Egor Ivanov <[email protected]> * fixes typos in readme Signed-off-by: Egor Ivanov <[email protected]> * removed ds_store Signed-off-by: Egor Ivanov <[email protected]> * upd .gitignore Signed-off-by: Egor Ivanov <[email protected]> --------- Signed-off-by: Egor Ivanov <[email protected]>
qameta · Jun 21, 2024 · cbea85a · cbea85a
1 parent 9cc67b0
commit cbea85a
Show file tree

Hide file tree

Showing 3 changed files with 15 additions and 10 deletions.
diff --git a/.gitignore b/.gitignore
@@ -1 +1,2 @@
 .idea/
+.DS_Store
diff --git a/README.md b/README.md
@@ -1,20 +1,24 @@
-# Allure TestOps deploy in kubernetes
+# Allure TestOps deploy in Kubernetes
 
 Here we give just a recap on how to deploy Allure TestOps in your own Kubernetes cluster using Helm chart maintained by Qameta Software Inc.
 
 ## Deploy description
 
 https://docs.qameta.io/allure-testops/install/kubernetes/
 
+## Support
+
+Chart is supported via https://help.qameta.io
+
 ## Database
 
 Do not deploy PostgreSQL using this chart. Such deployment is not suitable for production.
 
-Here we collected some recommendations for the database sconfiguration to ensure acceptable performance: https://docs.qameta.io/allure-testops/install/database/
+Here we collected some recommendations for the database configuration to ensure acceptable performance: https://docs.qameta.io/allure-testops/install/database/
 
 ## values.yaml template file
 
-1. Download the values temlate file from this very repo.
+1. Download the values template file from this very repo.
 
     https://github.com/qameta/allure-testops-deploy-helm-chart/blob/main/charts/allure-testops/values.yaml
 
@@ -33,7 +37,7 @@ helm upgrade --install testops qameta/testops -f values.yaml
 
 Application creates and updates the database schema to the actual state of selected release during its first run. This process could take considerable time, and readiness probes could fail, hence for the very first run, and in case of data migrations, we recommend disabling the probes.
 
-For the sake of this very example, we operating in the namespace `testops` which could differ from yours, so copy the comands copy and execute commands consciously after checking them against the reality.
+For the sake of this very example, we operating in the namespace `testops` which could differ from yours, so copy the commands copy and execute commands consciously after checking them against the reality.
 
 ```yaml
 helm upgrade --install testops qameta/testops \
@@ -46,13 +50,13 @@ helm upgrade --install testops qameta/testops \
 
 ## Allure TestOps release upgrade
 
-1. update values.yaml `version` to the most recent releae (see https://docs.qameta.io/allure-testops/release-notes/)
+1. update values.yaml `version` to the most recent release (see https://docs.qameta.io/allure-testops/release-notes/)
 
 ```yaml
-version: 5.3.2
+version: 5.3.3
 ```
 
-2. Run Helm `repo update` to get the most recent helm chart data, and then `helm upgrade`
+2. Run `helm repo update` to get the most recent helm chart data, and then `helm upgrade`
 
 ```bash
 helm repo update
@@ -122,4 +126,4 @@ Or alternatively you can deleted the namespace, then Kubernetes will remove all
 
 ```shell
 kubectl delete namespace testops
-```
+```
diff --git a/charts/testops/Chart.yaml b/charts/testops/Chart.yaml
@@ -1,9 +1,9 @@
 apiVersion: v2
 name: testops
-version: 5.3.2
+version: 5.3.3
 appVersion: 5.3.3
 
-description: Allure TestOps
+description: TestOps
 
 kubeVersion: '>= 1.14.0-0'