mirror of
https://github.com/komodorio/helm-dashboard.git
synced 2026-03-24 11:48:04 +00:00
81 lines
4.6 KiB
Markdown
81 lines
4.6 KiB
Markdown
# 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.
|
|
|
|
|
|
|
|
# Multicluster
|
|
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.
|
|
|
|
|
|
# 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.
|
|
|
|
|
|
# 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.
|
|
|
|
|
|
You can add the repository by clicking on 'Add Repository', as shown in the figure.
|
|
|
|
|
|
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.
|
|
|
|
|
|
Updating means refreshing your repository. You can update your repository as shown in the figure.
|
|
|
|
|
|
If you want to remove your repository from the Helm dashboard, click on the 'Remove' button as shown in the figure.
|
|
|
|
|
|
Use the filter option to find the desired chart quicker from the list of charts.
|
|
|
|
|
|
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.
|
|
|
|
|
|
# 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
|
|
|
|
|
|
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.
|
|
|
|
|
|
It indicates the version of chart that corresponds to this release.
|
|
|
|
|
|
A revision is linked to a release to track the number of updates/changes that release encounters.
|
|
|
|
|
|
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.
|
|
|
|
|
|
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.
|
|
|
|
|
|
Indication of upgrade possible/repo suggested.
|
|
|
|
|
|
# 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.
|
|
|
|
|
|
You can use the Upgrade/Downgrade button to switch to different release versions, as shown in the figure.
|
|
|
|
|
|
Confirm the upgrade settings and configuration and click on confirm button to continue
|
|
|
|
|
|
Once the upgrade is done, your release will show the status
|
|
|
|
|
|
It executes the test scripts or commands within the deployed application's environment and displays the results
|
|
|
|
|
|
Running test hooks results
|
|
|
|
|
|
|
|
|
|
|
|
|