Skip to content

Commit 0c38914

Browse files
committed
Address review comments
1 parent eed01ee commit 0c38914

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/spec/README.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
# Helm Controller
22

3-
The Helm Controller is a Kubernetes controller, allowing one to declaratively manage Helm chart
4-
releases with Kubernetes manifests.
3+
The Helm Controller is a [Kubernetes operator](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/),
4+
allowing one to declaratively manage Helm chart releases with Kubernetes manifests.
55

66
## Motivation
77

8-
The main goal is to provide an automated controller that can perform Helm actions (e.g.
8+
The main goal is to provide an automated operator that can perform Helm actions (e.g.
99
install, upgrade, uninstall, rollback, test) and continuously reconcile the state of Helm releases.
1010

1111
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.
1717
When dealing with an incident, one may wish to suspend the reconciliation of some Helm releases,
1818
without having to stop the reconciler and affect the whole cluster.
1919

20-
When operating a cluster, different teams may wish to receive notification about the status of
20+
When operating a cluster, different teams may wish to receive notifications about the status of
2121
their Helm releases. For example, the on-call team would receive alerts about all failures in
2222
the prod namespace, while the frontend team may wish to be alerted when a new version of the
2323
frontend chart was released, no matter the namespace.

0 commit comments

Comments
 (0)