Use this repository to submit NCSA Charts for Helm. Charts are curated application definitions for Helm. For more information about installing and using Helm, see its README.md. To get a quick introduction to Charts see this chart document.
This repository currently maintains the following Helm charts:
| Chart | Version | App Version | Description |
|---|---|---|---|
| elasticsearch2 | 0.2.2 | 2.4.6 | Elasticsearch 2.x deployment for legacy applications |
| fah | 1.0.2 | 8.4.9 | Folding@Home - Distributed computing for disease research |
| geoserver | 1.3.0 | 2.26.1 | Open source server for sharing geospatial data |
| mlflow | 1.2.1 | 2.2.1 | Open source platform for the machine learning lifecycle |
| uptime-kuma | 1.0.0 | 2.0.2 | Fancy self-hosted monitoring tool with 90+ notification integrations |
- elasticsearch2: Legacy Elasticsearch 2.x chart for applications requiring older Elasticsearch versions
- fah: Supports both CPU and GPU DaemonSets for distributed computing with configurable resource limits
- geoserver: GeoServer deployment with proxy configuration support and persistent storage options
- mlflow: Includes PostgreSQL and MinIO dependencies for complete ML lifecycle management
- uptime-kuma: Self-hosted monitoring with HTTP(s)/TCP/Ping monitoring, status pages, and notifications (
⚠️ requires local/block storage, no NFS)
For repository management guidelines and automation details, see AGENTS.md.
Add the NCSA chart repository to your Helm client:
helm repo add ncsa https://opensource.ncsa.illinois.edu/charts/
helm repo updateSearch available charts:
helm search repo ncsaInstall a chart from the NCSA repository:
helm install my-release ncsa/<chart-name>For example, to install the Folding@Home chart:
helm install fah ncsa/fahFor more information on using Helm, refer to the Helm documentation.
.
├── .github/workflows/ # Automated workflows for chart updates
├── charts/ # Chart source files
│ ├── elasticsearch2/
│ ├── fah/
│ ├── geoserver/
│ ├── mlflow/
│ └── uptime-kuma/
├── AGENTS.md # Repository guidelines and automation
└── README.md # This file
Each chart directory contains:
Chart.yaml- Chart metadata and version informationvalues.yaml- Default configuration valuesREADME.md- Chart-specific documentationCHANGELOG.md- Version historytemplates/- Kubernetes manifest templates
We welcome contributions to improve existing charts or add new ones!
- See AGENTS.md for detailed repository management guidelines
- Each chart has automated version checking via GitHub Actions
- All changes must go through pull requests (no direct pushes)
- Charts should maintain a CHANGELOG.md with version history
To maintain a chart, you need to:
- Be listed as a maintainer in the chart's
Chart.yamlfile - Be invited as a collaborator on this repository
- Add an
OWNERSfile to the chart directory listing reviewers and approvers
- Pull requests require review and approval before merging
- Automated workflows handle version updates and create PRs
- Stale PRs (inactive for 30+ days) will be automatically closed
For issues or questions:
- Open an issue in this repository
- Contact the chart maintainers listed in each chart's
Chart.yaml