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
This issue is about supporting Kubernetes Probes from the framework.
The main question is how to map probes to operators in general:
Liveness - is operator started? (So start method called?) Is there any other meaningful way?.
Should be this bound to sync timeout: Event Source Sync Timeout #1318 ? So if out of sync it is basically not alive?
Readyness (or Startup?) - probes is naturally can be bidden to event source sync, so the operator is ready when event sources are already synced.
The API:
Operatoroperator = newOperator()
...
operator.start()
// from this point the methodsbooleanready = operator.isReady()
booleanalive = operator.isAlive()
User later can call those methods from a servlet container or whatever integration chooses with K8S for the probes.
The text was updated successfully, but these errors were encountered:
So probably the operator is not ready if the informers are not watching.
But this is related also with the issue: #1405
Where we want to start informers, and if there is not permission for the informer (and not watching) that is fine.
This however this probably requires explicit checking of permission.
This issue is about supporting Kubernetes Probes from the framework.
The main question is how to map probes to operators in general:
Liveness - is operator started? (So start method called?) Is there any other meaningful way?.
Should be this bound to sync timeout: Event Source Sync Timeout #1318 ? So if out of sync it is basically not alive?
Readyness (or Startup?) - probes is naturally can be bidden to event source sync, so the operator is ready when event sources are already synced.
The API:
User later can call those methods from a servlet container or whatever integration chooses with K8S for the probes.
The text was updated successfully, but these errors were encountered: