You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/src/BINDING_VALIDATING.md
+12-3Lines changed: 12 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -104,7 +104,7 @@ See example [204-validating-webhook](./examples/204-validating-webhook).
104
104
105
105
> Note that the `group` parameter is only for including snapshots. `kubernetesValidating` hook is never executed on `schedule` or `kubernetes` events with binding context with `"type":"Group"`.
106
106
107
-
The hook receives a binding context and should return response in `$VALIDATING_RESPONSE_PATH`.
107
+
The hook receives a binding context and should return response in `$VALIDATING_RESPONSE_PATH` (also available as `$ADMISSION_RESPONSE_PATH`).
108
108
109
109
$BINDING_CONTEXT_PATH file example:
110
110
@@ -242,8 +242,17 @@ Command line options:
242
242
A path to a ca certificate for ValidatingWebhookConfiguration. Can be set
executeHookOnSynchronization: true|false # default is true
169
+
waitForSynchronization: true|false # default is true
158
170
keepFullObjectsInMemory: true|false # default is true
171
+
resynchronizationPeriod: "1h"
159
172
nameSelector:
160
173
matchNames:
161
174
- pod-0
@@ -244,6 +257,10 @@ kubernetes:
244
257
245
258
- `keepFullObjectsInMemory`— if not set or `true`, dumps of Kubernetes resources are cached for this binding, and the snapshot includes them as `object` fields. Set to `false` if the hook does not rely on full objects to reduce the memory footprint.
246
259
260
+
- `waitForSynchronization`— if `false`, Shell-operator will not wait for a hook's Synchronization to complete before processing further events for named queues. Default is `true`. Can only be set to `false` when `queue` is also explicitly specified.
261
+
262
+
- `resynchronizationPeriod`— a period in Go duration format (e.g. `1h`, `30m`) after which a full resynchronization (re-list + re-watch) of Kubernetes objects is issued for this binding. Useful to recover from missed watch events.
263
+
247
264
- `group`— a key that define a group of `schedule` and `kubernetes` bindings. See [grouping](#binding-context-of-grouped-bindings).
248
265
249
266
#### Example
@@ -353,7 +370,7 @@ Objects should match all expressions defined in `fieldSelector` and `labelSelect
353
370
354
371
### kubernetesValidating
355
372
356
-
Use a hook as handler for [ValidationWebhookConfiguration][admission-controllers].
373
+
Use a hook as handler for [ValidatingWebhookConfiguration][admission-controllers].
357
374
358
375
See syntax and parameters in [BINDING_VALIDATING.md](BINDING_VALIDATING.md)
359
376
@@ -369,7 +386,7 @@ When an event associated with a hook is triggered, Shell-operator executes the h
369
386
370
387
Temporary files have unique names to prevent collisions between queues and are deleted after the hook run.
371
388
372
-
Binging context is a JSON-array of structures with the following fields:
389
+
Binding context is a JSON-array of structures with the following fields:
373
390
374
391
- `binding`— a string from the `name` parameter. If this parameter has not been set in the binding configuration, then strings "schedule" or "kubernetes" are used. For a hook executed at startup, this value is always "onStartup".
375
392
- `type`— "Schedule" for `schedule` bindings. "Synchronization" or "Event" for `kubernetes` bindings. "Group" if `group` is defined.
0 commit comments