Files
helm-dashboard/FEATURES.md
S Kumar Dhananjaya e8fe75e433 FEATURES.md file #255 (#425)
* Updated FEATURES.md file

* Update FEATURES.md
2023-07-06 09:34:47 +01:00

4.6 KiB

Shutting down the app

To close Helm-dashboard, click on the button in the rightmost corner of the screen. Once you click on it, your Helm-dashboard will be shut down.

Shutdown_screenshot

Multicluster

If you want to switch to a different cluster, simply click on the corresponding cluster as shown in the figure. Click here to learn how to access multiple clusters. Multicluster_screenshot

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

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. You can find the repository in the home section, as depicted in the figure. Repository3

You can add the repository by clicking on 'Add Repository', as shown in the figure. Repository

After completing that step, enter the following data: the repository name and its URL. You can also add the username and password, although this is optional. Repository2

Updating means refreshing your repository. You can update your repository as shown in the figure. Repository4

If you want to remove your repository from the Helm dashboard, click on the 'Remove' button as shown in the figure. Repository5

Use the filter option to find the desired chart quicker from the list of charts. Repository6

If you want to install a particular chart, simply hover the pointer over the chart name and an 'Install' button will appear, as shown in the figure. Repository7

Installed Releases list

A release is an instance of your selected chart running on your Kubernetes Cluster. That means every time that you install a Helm chart there, it creates a new release or instance that coexists with other releases without conflict. You can filter releases based on namespaces or search for release names Releases

The squares represent k8s resources installed by the release. Hover over each square to view a tooltip with details. Yellow indicates "pending," green signifies a healthy state, and red indicates an unhealthy state. Releases1

It indicates the version of chart that corresponds to this release. Releases2

A revision is linked to a release to track the number of updates/changes that release encounters. Releases3

Namespaces are a way to organize clusters into virtual sub-clusters — they can be helpful when different teams or projects share a Kubernetes cluster. Any number of namespaces are supported within a cluster, each logically separated from others but with the ability to communicate with each other. Releases4

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

Indication of upgrade possible/repo suggested. Release6

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

You can use the Upgrade/Downgrade button to switch to different release versions, as shown in the figure. Detail1

Confirm the upgrade settings and configuration and click on confirm button to continue Detail2

Once the upgrade is done, your release will show the status Detail3

It executes the test scripts or commands within the deployed application's environment and displays the results Detail4

Running test hooks results Detail5