Sorry, my mistake, it seems that the ready=True is due to `initialDelaySeconds` has been set `30s`, and within the 30 seconds, the nginx POD would be `Ready`.
BTW, `initialDelaySeconds` is likely to said `I'm not ready in this period, and it's ok, I need some time to warm up`, but POD status has been set to `Ready=True`. As I known, in marathon, the similar parameter `graceperiodseconds` will mark the task healthcheck status as `unknown`, I think this state should be better to trigger the pod real state. Thanks. -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
