Merge branch 'helm-dashboard-v2' of https://github.com/komodorio/helm…

…-dashboard into fix-cluster-change

FEATURES.md

@@ -25,6 +25,16 @@ If you want to switch to a different cluster, simply click on the corresponding
 figure. You
 can [read here](https://kubernetes.io/docs/tasks/access-application-cluster/configure-access-multiple-clusters/) to
 learn on how to configure access to multiple clusters.
+# Reset Cache
+The "Reset Cache" feature in Helm Dashboard clears the cached data and fetches the latest information from the backend or data source. It ensures that the dashboard displays up-to-date data and reflects any recent changes or updates.
+![Detail1](images/screenshot_reset_cache.png)
+
+# Repository
+Essentially, a repository is a location where charts are gathered and can be shared. If you want to learn more about repositories, [click here](https://helm.sh/docs/topics/chart_repository/). You can find the repository in the home section, as depicted in the figure.
+![Repository3](images/screenshot_repository3.png)
+
+You can add the repository by clicking on 'Add Repository', as shown in the figure.
+![Repository](images/screenshot_repository.png)
 
 ## Installed Releases List
 
@@ -52,14 +62,33 @@ Updated" refers to the amount of time that has passed since the last revision of
 upgrade the release, a new revision is created. You can think of it as the "age" of the latest revision.
 ![Releases5](images/screenshot_release5.png)
 
+Indication of upgrade possible/repo suggested.
+![Release6](images/screenshot_upgrade_available.png)
+
 ## Release details
 
 This indicates the status of the deployed release, and 'Age' represents the amount of time that has passed since the
 creation of the revision until now.
 ![Detail](images/screenshot_release_detail.png)
 
 You can use the Upgrade/Downgrade button to switch to different release versions, as shown in the figure.
-![Detail1](images/screenshot_release_detail1.png)
+![Detail1](images/screenshot_upgrade_available2.png)
+
+Confirm the upgrade settings and configuration and click on confirm button to continue
+![Detail2](images/screenshot_upgrade_confirmation.png)
+
+Once the upgrade is done, your release will show the status 
+![Detail3](images/screenshot_upgrade_complete.png)
+
+It executes the test scripts or commands within the deployed application's environment and displays the results
+![Detail4](images/screenshot_run_tests.png)
+
+Running test hooks results 
+![Detail5](images/screenshot_test_results.png)
+
+
+
+
 
 ### Execute Helm tests
 

Makefile

@@ -1,5 +1,5 @@
 DATE ?= $(shell date +%FT%T%z)
-VERSION ?= $(git describe --tags --always --dirty --match=v* 2> /dev/null || \
+VERSION ?= $(shell git describe --tags --always --dirty --match=v* 2> /dev/null || \
  cat $(CURDIR)/.version 2> /dev/null || echo "v0")
 
 .PHONY: test

charts/helm-dashboard/templates/deployment.yaml

@@ -60,11 +60,11 @@ spec:
  livenessProbe:
  httpGet:
  path: /status
- port: http
+ port: 8080
  readinessProbe:
  httpGet:
  path: /status
- port: http
+ port: 8080
  resources:
  {{- toYaml .Values.resources | nindent 12 }}
  volumeMounts: