Skip to content

Commit 7ce83e1

Browse files
Apply suggestions from code review
Co-authored-by: Malte Sander <malte.sander.it@gmail.com>
1 parent 8c213a3 commit 7ce83e1

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

modules/concepts/pages/overrides.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -155,10 +155,10 @@ They will *not* be applied to:
155155
== Object overrides
156156

157157
Sometime you need to override Kubernetes objects other than the generated Pods, e.g. ServiceAccounts or the StatefulSet/Deployment/DaemonSet.
158-
Object overrides allow you to override any Kubernetes object the operator creates are part of it's reconciliation loop, which basically means all objects that are created for a given stacklet.
158+
Object overrides let you modify any Kubernetes resource that the operator creates as part of its reconciliation loop, which essentially includes all objects associated with a given stacklet.
159159

160-
On every Stackable CRD that get's reconciled into a set of Kubernetes objects we offer a field `.spec.objectOverrides`.
161-
You can set it to a list of arbitrary YAML objects, which need to be valid Kubernetes objects.
160+
On every Stackable CRD that is reconciled into a set of Kubernetes objects we provide the field `.spec.objectOverrides`.
161+
This field accepts a list of arbitrary YAML objects, each of which must be a valid Kubernetes resource.
162162

163163
For every resource it creates, the operator processes the list of overrides from top to bottom.
164164
It first checks if an override matches the resource being created by comparing the `apiVersion`, `kind`, `name` and if applicable `namespace` (cluster-scoped resources may omit the namespace).

0 commit comments

Comments
 (0)