Helm Marketplace
The Helm Marketplace in Atmosly provides a centralized hub for discovering, configuring, and deploying Helm charts to your Kubernetes clusters. You can browse curated and third-party charts, add your own Helm repositories, and manage deployed releases — all from a single interface.
Chart Sources
Charts in the Marketplace are organized into three categories:
| Category | Description |
|---|---|
| Atmosly | Curated charts maintained by Atmosly for common infrastructure and platform tooling. |
| User Managed | Charts from Helm repositories you have added to Atmosly. |
| Others | Charts from popular public repositories — Bitnami, Elastic, and Prometheus Community. |
Browsing Charts
Navigate to Marketplace from the left menu to browse available Helm charts.
Filtering
The left sidebar lets you filter charts by category and repository:
- Select a category tab — Atmosly, User Managed, or Others.
- Check one or more repositories within the selected category.
- Charts from the selected repositories are displayed as cards in the main area.
Search
Use the search bar at the top to filter charts by name. The search matches against chart names and provider names.
Chart Cards
Each chart is displayed as a card showing:
| Field | Description |
|---|---|
| Icon | The chart's logo or icon. |
| Provider | The repository or provider the chart belongs to. |
| Chart Name | The name of the Helm chart. |
| Chart Version | The latest available version. |
Click on a chart card to view its details and deploy it.
Chart Details
Clicking a chart card opens the chart detail page with three tabs:
Values.yaml
A full YAML editor displaying the chart's default values.yaml file. You can edit the values directly before deploying. Changes are sent as overrides — the original values are preserved.
Basic Details
| Field | Description |
|---|---|
| Name | Chart name. |
| Description | A summary of what the chart deploys. |
| Home | The chart's homepage URL. |
| App Version | The application version packaged in the chart. |
| Source | Link to the chart's source code repository. |
ReadMe
The chart's README documentation rendered as formatted text, including usage instructions, configuration options, and examples.
Deploying a Chart
From the chart detail page, fill in the deployment form on the left panel:
| Field | Description |
|---|---|
| App Name | A unique release name for this deployment. Must be lowercase letters and hyphens only, 3–50 characters. |
| Cluster | The target Kubernetes cluster. Only active clusters with ArgoCD installed are eligible. |
| Namespace | The Kubernetes namespace where the chart will be deployed. Select an existing namespace or type a new one. |
| Chart Version | Select the version of the chart to deploy. All available versions are listed in the dropdown. |
Customizing Values
Edit the values.yaml content in the YAML editor tab before deploying. Your modifications are sent as value overrides — the chart's default values are preserved as a base.
Deploy
Click Deploy to submit the deployment. You will be navigated to the cluster's Helm releases list where you can monitor the deployment status.
The target cluster must have ArgoCD installed for chart deployment. If ArgoCD is not installed, the deploy button will be disabled with an appropriate message.
Helm Repositories
Adding a Repository
- Click Add Repositories in the top-right corner of the Marketplace page.
- Fill in the repository details:
| Field | Description |
|---|---|
| Repository Type | Public — no authentication required. Private — requires credentials. |
| Name | A display name for the repository. |
| URL | The Helm repository URL (must serve a valid index.yaml). |
| Username | Username for private repositories. |
| Password | Password for private repositories. |
- Click Add Repo to save.
Allow up to 5 minutes for Atmosly to load and index charts from a newly added repository.
Editing a Repository
- In the left sidebar under User Managed, locate your repository.
- Click the edit icon next to the repository name.
- Update the fields as needed and click Update.
Deleting a Repository
- In the left sidebar under User Managed, locate your repository.
- Click the delete icon next to the repository name.
- Confirm the deletion.
Deleting a repository removes it from the Marketplace. Existing releases deployed from this repository are not affected — they will continue to run on the cluster.
Deployment History
Navigate to the Deployment History section within the Marketplace module to view all Helm chart deployments across your organization.
| Column | Description |
|---|---|
| App Name | The release name given during deployment. |
| Chart Name | The Helm chart that was deployed. |
| Chart Version | The deployed chart version. |
| Cluster | The cluster where the chart is deployed. |
| Deployment Date | When the deployment was created or last updated. |
| Namespace | The Kubernetes namespace of the deployment. |
| Status | The current release phase (see table below). |
Click on a deployment to navigate to its cluster's Helm releases view for detailed management.
Release Statuses
| Status | Description |
|---|---|
| Deploying | The chart is being deployed to the cluster. |
| Deployed | The chart was successfully deployed and is running. |
| Deploy Failed | The deployment failed. Check logs for details. |
| Updating | The release is being updated with new values or a new chart version. |
| Update Failed | The update operation failed. |
| Deleting | The release is being uninstalled from the cluster. |
| Delete Failed | The uninstallation failed. |
| Deleted | The release has been successfully uninstalled. |
Application Health Statuses
After deployment, Atmosly monitors the health of the deployed application:
| Status | Description |
|---|---|
| Healthy | The application is running and all resources are in a good state. |
| Unhealthy | The application has errors or failing resources. |
| Progressing | The application is being rolled out or updated. |
| Unknown | The health status cannot be determined. |
| Missing | Expected application resources are not found on the cluster. |
| Degraded | The application is partially available or experiencing issues. |
| Suspended | The application has been suspended or paused. |
Managing Releases
Deployed Helm releases are managed from the cluster's Helm Charts section (accessible from Cluster Details).
Upgrading a Release
- Navigate to the deployed release from the cluster's Helm Charts list.
- Modify the
values.yamloverrides or select a new chart version. - Click Update to apply the changes.
A new version entry is created in the release's version history. The release status changes to Updating during the upgrade.
Rolling Back a Release
- Navigate to the deployed release.
- Open the Version History to view all past deployment versions.
- Select a previous version and click to roll back.
The rollback creates a new version entry with the values from the selected historical version.
Deleting a Release
- Navigate to the deployed release.
- Click Delete to uninstall the Helm release from the cluster.
- Confirm the deletion.
The release status changes to Deleting and then to Deleted once uninstallation completes. Deleted releases remain visible in the deployment history for audit purposes.
Version History
Each deployed release maintains a full version history:
| Field | Description |
|---|---|
| Version Number | Sequential version counter (0, 1, 2, ...). |
| Values | The values.yaml overrides used for this version. |
| Updated At | When this version was deployed. |
| Updated By | The user who triggered the deployment or update. |
| Status | The deployment status of this version. |
You can view and compare values across versions to understand what changed between deployments.
Permissions
| Permission | Description |
|---|---|
| View marketplace | Browse charts, view repositories, and view deployment history. |
| Deploy helm charts | Deploy charts to clusters. |
| Update helm charts | Update deployed releases with new values or versions. |
| Delete helm charts | Uninstall deployed releases from clusters. |
| Manage repositories | Add, edit, and delete Helm repositories. |