FEATURES.md file #255 (#425)

* Updated FEATURES.md file * Update FEATURES.md
komodorio · Jul 6, 2023 · e8fe75e · e8fe75e
1 parent aa79f67
commit e8fe75e
Show file tree

Hide file tree

Showing 10 changed files with 24 additions and 1 deletion.
diff --git a/FEATURES.md b/FEATURES.md
@@ -7,6 +7,10 @@ To close Helm-dashboard, click on the button in the rightmost corner of the scre
 If you want to switch to a different cluster, simply click on the corresponding cluster as shown in the figure. [Click here](https://kubernetes.io/docs/tasks/access-application-cluster/configure-access-multiple-clusters/) to learn how to access multiple clusters.
 ![Multicluster_screenshot](images/screenshot_multicluster.png)
 
+# 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)
@@ -48,10 +52,29 @@ Namespaces are a way to organize clusters into virtual sub-clusters — they can
 Updated" refers to the amount of time that has passed since the last revision of the release. Whenever you install or 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)
+
+
+
+
 
diff --git a/images/screenshot_reset_cache.png b/images/screenshot_reset_cache.png
diff --git a/images/screenshot_run_test.png b/images/screenshot_run_test.png
diff --git a/images/screenshot_run_test_result.png b/images/screenshot_run_test_result.png
diff --git a/images/screenshot_run_tests.png b/images/screenshot_run_tests.png
diff --git a/images/screenshot_test_results.png b/images/screenshot_test_results.png
diff --git a/images/screenshot_upgrade_available.png b/images/screenshot_upgrade_available.png
diff --git a/images/screenshot_upgrade_available2.png b/images/screenshot_upgrade_available2.png
diff --git a/images/screenshot_upgrade_complete.png b/images/screenshot_upgrade_complete.png
diff --git a/images/screenshot_upgrade_confirmation.png b/images/screenshot_upgrade_confirmation.png