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.
For general Helm Chart discussions join the Helm Charts (#charts) room in the Kubernetes.
For issues and support for Helm and Charts see Support Channels.
To add the Incubator charts for your local client, run helm repo add:
$ helm repo add ncsa https://opensource.ncsa.illinois.edu/charts/
"ncsa" has been added to your repositories
You can then run helm search ncsa to see the charts.
After installing the helm repository (see above), you can use helm install ncsa/<chart>.
For more information on using Helm, refer to the Helm's documentation.
Take a look at the alpine example chart and the nginx example chart for reference when you're writing your first few charts.
Before contributing a Chart, become familiar with the format. Note that the project is still under active development and the format may still evolve a bit.
This GitHub repository contains the source for the packaged and versioned charts released in the https://opensource.ncsa.illinois.edu/charts/ (the Chart Repository).
The Charts in the ncsa/ directory in the master branch of this repository match the latest packaged Chart in the Chart Repository, though there may be previous versions of a Chart available in that Chart Repository.
The purpose of this repository is to provide a place for maintaining and contributing official Charts, with CI processes in place for managing the releasing of Charts into the Chart Repository.
Individual charts can be maintained by one or more users of GitHub. When someone maintains a chart they have the access to merge changes to that chart. To have merge access to a chart someone needs to:
- Be listed on the chart, in the
Chart.yamlfile, as a maintainer. If you need sponsors and have contributed to the chart, please reach out to the existing maintainers, or if you are having trouble connecting with them, please reach out to one of the OWNERS of the charts repository. - Be invited (and accept your invite) as a read-only collaborator on this repo. This is required for @k8s-ci-robot PR comment interaction.
- An OWNERS file needs to be added to a chart. That OWNERS file should list the maintainers' GitHub login names for both the reviewers and approvers sections. For an example see the Drupal chart. The
OWNERSfile should also be appended to the.helmignorefile.
Once these three steps are done a chart approver can merge pull requests following the directions in the REVIEW_GUIDELINES.md file.
For information related to the review procedure used by the Chart repository maintainers, see Merge approval and release process.
Pull Requests and Issues that have no activity for 30 days automatically become stale. After 30 days of being stale, without activity, they become rotten. Pull Requests and Issues can rot for 30 days and then they are automatically closed. This is the standard stale process handling for all repositories on the Kubernetes GitHub organization.
This chart repository supports the latest and previous minor versions of Kubernetes. For example, if the latest minor release of Kubernetes is 1.8 then 1.7 and 1.8 are supported. Charts may still work on previous versions of Kubernertes even though they are outside the target supported window.
To provide that support the API versions of objects should be those that work for both the latest minor release and the previous one.
This project is still under active development, so you might run into issues. If you do, please don't be shy about letting us know, or better yet, contribute a fix or feature.