@@ -9,7 +9,7 @@ A Kubernetes Controller is a routine running in a Kubernetes cluster that watche
9
9
update / delete events on Resources, and triggers a Reconcile function in response. Reconcile
10
10
is a function that may be called at any time with the Namespace and Name of an object (Resource
11
11
instance), and it will make the cluster state match the state declared in the object Spec.
12
- Upon completion, Reconcile updates the object Status the new actual state.
12
+ Upon completion, Reconcile updates the object Status to the new actual state.
13
13
14
14
It is common for Controllers to watch for changes to the Resource type that they Reconcile
15
15
* and* Resource types of objects they create. e.g. a ReplicaSet Controller watches for
@@ -69,11 +69,11 @@ rollout before starting the next.
69
69
70
70
## Watching Events
71
71
72
- The Controller Reconcile is triggered both by cluster events.
72
+ The Controller Reconcile is triggered by cluster events.
73
73
74
74
##### Watching Resources
75
75
76
- Controllers must watch for events for the Resource they Reconcile. The ReplicaSetController
76
+ Controllers must watch for events for the Resource they Reconcile. The ReplicaSetController
77
77
watches for changes to ReplicaSets and triggers a Reconcile in response.
78
78
79
79
###### ReplicaSet Creation
@@ -157,7 +157,7 @@ Instead the Controller must write back the Status of the object at each Reconcil
157
157
users must check the object Status.
158
158
159
159
{% panel style="info", title="Status" %}
160
- The controller will keep Status up-to-date both in response to user initiated events, but also
160
+ The controller will keep Status up-to-date not only in response to user initiated events, but also
161
161
in response to non-user initiated events, such as Node failures.
162
162
{% endpanel %}
163
163
0 commit comments