Skip to content
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
41 lines (26 sloc) 3.1 KB

Apply Waiting

kapp includes builtin rules on how to wait for the following resource types:

If resource is not affected by the above rules, its waiting behaviour depends on aggregate of waiting states of its associated resources (associated resources are resources that share same label value).

Controlling waiting via resource annotations

  • annotation controls whether waiting will happen at all. Possible values: ``.
  • annotation controls whether associated resources impact resource's waiting state. Possible values: ``.

apps/v1/Deployment resource

kapp by default waits for apps/v1/Deployment resource to have status.unavailableReplicas equal to zero. Additionally waiting behaviour can be controlled via following annotations:

  • annotation controls how many new available replicas are enough to consider waiting successful. Example values: "10", "5%".

Custom waiting behaviour

(This behaviour has not been enabled. Please reach out on slack for more info.)

kapp can be extended with custom waiting behaviour through resource annotations. Controllers/operators can update resource annotations to indicate resource's reconcilation state.

If resource has below annotations, kapp will wait for reconcile state to become either ok or fail.

  • indicates current reconcilation state. Possible values: ok, fail, ongoing.
  • includes additional information about current reconcilation state.

Note that it's recommended to have a mutating webhook hook to reset annotation to ongoing upon resource creation or update to avoid race between kapp and controller updating annotations.

You can’t perform that action at this time.