fluxcd
/
helm-controller
mirror of https://github.com/fluxcd/helm-controller.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Address review comments

This commit is contained in:
Sean Eagan 2020-09-29 07:51:49 -05:00 committed by Hidde Beydals
parent 60e1d06c1a
commit d8c0c38203
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/spec/README.md
View File

@ -1,11 +1,11 @@
# Helm Controller # Helm Controller
The Helm Controller is a Kubernetes controller, allowing one to declaratively manage Helm chart The Helm Controller is a [Kubernetes operator](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/),
releases with Kubernetes manifests. allowing one to declaratively manage Helm chart releases with Kubernetes manifests.
## Motivation ## Motivation
The main goal is to provide an automated controller that can perform Helm actions (e.g. The main goal is to provide an automated operator that can perform Helm actions (e.g.
install, upgrade, uninstall, rollback, test) and continuously reconcile the state of Helm releases. install, upgrade, uninstall, rollback, test) and continuously reconcile the state of Helm releases.
When provisioning a new cluster, one may wish to install Helm releases in a specific order, for When provisioning a new cluster, one may wish to install Helm releases in a specific order, for
@ -17,7 +17,7 @@ and this chart needs to be installed first.
When dealing with an incident, one may wish to suspend the reconciliation of some Helm releases, When dealing with an incident, one may wish to suspend the reconciliation of some Helm releases,
without having to stop the reconciler and affect the whole cluster. without having to stop the reconciler and affect the whole cluster.
When operating a cluster, different teams may wish to receive notification about the status of When operating a cluster, different teams may wish to receive notifications about the status of
their Helm releases. For example, the on-call team would receive alerts about all failures in their Helm releases. For example, the on-call team would receive alerts about all failures in
the prod namespace, while the frontend team may wish to be alerted when a new version of the the prod namespace, while the frontend team may wish to be alerted when a new version of the
frontend chart was released, no matter the namespace. frontend chart was released, no matter the namespace.