Ryan Luckieandk8s-ci-robot
75e341de7b
* [stable/stolon] add stolon chart * Requested changes from reviewers - update image.pullPolicy - update backend to use consul by default - remove resource specs - remove unused partials - update apiVersion - remove obsolete annotation - update persistence spec to align with best practices - fix case in values.yaml * don't install etcd by default * Refactor service and port definitions - refactor service manifests to allow more granular configuration - update port definitions in values.yaml * Numerous fixes for issues found during testing - remove stolon.clusterName partial from _helpers.tpl and change manifests accordingly - fix create-secrets-job - refactor labels and selectors in all manifests to align with best practices - add keeper-headless-service for statefulset * Changes to fix kubernetes as backend store - update label.app to support stolon requirements - see https://github.com/sorintlab/stolon/commit/38ae6b13b5e161a5bfe0fbe01084ca060eaf2e76#diff-95cdd374e9440fde010ff35d65f8cf3fR54 - add .Values.store.kubeResourceKind - make kubernetes default store in Values.yaml - remove subcharts for consul and etcd - add nodeSelector, affinity and toleration for keeper-statefulset - clean up values.yaml - update README to reflect changes * Requsted changes, cleanup, misc fixes - update image to latest version of stolon - remove create-secrets-job and use native secrets w/ {{ if .Release.IsInstall }} to avoid overwriting secrets - remove unnecessary keeper service - remove unused template - cleanup labels and selectors - add component and stolon-cluster labels to support discovery in latest version of stolon - add annotations to services, deployment and statefulset - enable stolon metrics * Add pgParameters option - add ability to add postgresql.conf config options - update create-cluster-job to use new config options - remove deprecated config options - update README and values.yaml - move to master-pg10 image tag * Requested changes - revert to use stable stolon image - add etcdImage to values - fix indent - remove initContainer annotation and replace with proper spec - add component label to selector specs * Fix resource definitions
Helm Charts
Use this repository to submit official Charts for Kubernetes Helm. Charts are curated application definitions for Kubernetes Helm. For more information about installing and using Helm, see its README.md. To get a quick introduction to Charts see this chart document.
Where to find us
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.
How do I install these charts?
Just helm install stable/<chart>. This is the default repository for Helm which is located at https://kubernetes-charts.storage.googleapis.com/ and is installed by default.
For more information on using Helm, refer to the Helm's documentation.
How do I enable the Incubator repository?
To add the Incubator charts for your local client, run helm repo add:
$ helm repo add incubator https://kubernetes-charts-incubator.storage.googleapis.com/
"incubator" has been added to your repositories
You can then run helm search incubator to see the charts.
Chart Format
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.
Repository Structure
This GitHub repository contains the source for the packaged and versioned charts released in the gs://kubernetes-charts Google Storage bucket (the Chart Repository).
The Charts in the stable/ 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.
The Charts in this repository are organized into two folders:
- stable
- incubator
Stable Charts meet the criteria in the technical requirements.
Incubator Charts are those that do not meet these criteria. Having the incubator folder allows charts to be shared and improved on until they are ready to be moved into the stable folder. The charts in the incubator/ directory can be found in the gs://kubernetes-charts-incubator Google Storage Bucket.
In order to get a Chart from incubator to stable, Chart maintainers should open a pull request that moves the chart folder.
Contributing a Chart
We'd love for you to contribute a Chart that provides a useful application or service for Kubernetes. Please read our Contribution Guide for more information on how you can contribute Charts.
Note: We use the same workflow, License and Contributor License Agreement as the main Kubernetes repository.
Owning and Maintaining A Chart
Individual charts can be maintained by one or more members of the Kubernetes community. When someone maintains a chart they have the access to merge changes to that chart. To have merge access to a chart someone first needs to be listed on the chart, in the Chart.yaml file, as a maintainer. If that is the case there are two steps that need to happen:
- Become a member of the Kubernetes community. If you need sponsors and have contributed to charts please reach out to one of the OWNERS of the charts repository.
- 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 two steps are done a chart approver can merge pull requests following the directions in the REVIEW_GUIDELINES.md file.
Review Process
For information related to the review procedure used by the Chart repository maintainers, see Merge approval and release process.
Stale Pull Requests and Issues
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.
Supported Kubernetes Versions
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.
Status of the Project
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.