I have a springboot based app which contains following component.
- Atomix-raft(Distributed data structure)
- Netty Server
- External database.
We start first atomix-raft then Netty and then calling Springboot app started. Thats how dependency are created.
As, i am adding readinessProbe, each pod is blocking traffic[all external(outside of namespace) & internal (within namespace), both including its peers pods) since default initial value for readinessProbe is failure, if you are adding it. We have atomix-raft (DDS), to bring atomix-raft up, it needs to communicate with its peers to come on consensus and electing leader. So atomix is not able bringing up since can’t communicate with its peers. Hence app is not able being ready. So its a loop problem.
We need somehow mechanism to have intial readinessProbe value as success, till app comes up.
General Discussions #readinessProbe #probe #health k8s-blog service