I have a question regarding the technical working of Rancher. The main advantage we thought to accomplish with Rancher and Kubernetes was, that whenever there is an instance of an application failing due to whatever reason, rancher automatically deploys another one so that you have no downtime.
In our situation however, we regularly experience a situation where the application stops and does not automatically redeploy a new pod and removes the ‘broken’ pod.
But in some situations (the reason is unknown), the whole service suddenly stops working, because one pod is failing. So that is the first thing that we don’t understand: why is the whole service unavailable while there is still one active and running? See screenshot below for the error situation:
The other question that we can not resolve is: why is rancher not automatically redeploying the failing pod? When I click on the button ‘redeploy’ in the service, the whole service works again in a few seconds. In my understanding, this should happen as soon as rancher detects that the service is unstable, but this can only be accomplished by manually clicking ‘redeploy’.
Hopefully somebody understands my problem and knows how to fix this. Thanks in advance!