getLastRequest()but looks like once is conusmed in one of the test cases the next time we try to get the body is blocked forever, like if the buffer is not there anymore, do you know what could be?
In fabric 8 kubernetes client, when Reflector receives a watch event, it seems to pass the event to the SyncerStore.
In client-go, it seems to be put in a queue called
Can I understand that the abstraction is different without
DeltaFIFO in fabric 8 kubernetes client?
The above Processor store
resync method only seems to trigger the
Update notification once again.
I understood The resync plays back all the events held in the informer cache.
Does this logic have any purpose other than giving the controller one more notification?
Is there are way to list all pods for a jenkins instance and see which ones are down by using https://github.com/fabric8io/kubernetes-client ?
For example, if I run the following command "kubectl get pod --all-namespaces -o wide" I will get "Namespace", "NAME", "Status" etc. I want to get all pods/agents which STATUS is set to "Error"
It is said that kubernetes uses
level-trigger, but in fact, watch or informer api is an
edge trigger rather than a level trigger, isn't it?
If an event is lost due to a network issue, the watch or informer api loses the new desired state.
If we use the polling method, It can be thought of as a level trigger but I think that the event-driven method as a watch or informer is close to an eade trigger.
KubernetesServerin unit tests. Are there any known issues regarding this (I couldn't find any but maybe I have missed something)? Otherwise I would try to raise an issue on GitHub including a small reproduction example.