Statefulsets: Populating DNS records for the pods even when they are not ready

[prpl]

Hi All,

1. As you all know, the DNS records for the statefulset pods using headless services are populated based on the readinessProbe statuses
   
2. But in some scenarios, the pods might want to communicate with other pods in the same statefulset to come to a ready state. This also means, the other pods initiate communications with this new pods (which are still not ready). For instances, add the node pods to the established cluster)
3. Since the DNS records would not be populated, the inter-pod communication is broken till the pods come to ready state.
4. From a non-headless service fronting the pods, it makes sense to use the readiness probes to populate the endpoints. But wondering if the same approach is required for headless services used by  statefulset pods

regards,

prpl

[John Belamaric]

Hi prpl,

See https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.10/#servicespec-v1-core, in particular publishNotReadyAddresses.

John

--
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-de...@googlegroups.com.
To post to this group, send email to kuberne...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/84efaca5-e1fd-4161-b8a6-46259a451950%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[prpl]

Thanks John, it was a perfect solution!

On Tuesday, May 1, 2018 at 8:24:25 PM UTC+5:30, John Belamaric wrote:

Hi prpl,

See https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.10/#servicespec-v1-core, in particular publishNotReadyAddresses.

John

On May 1, 2018, at 5:09 AM, prpl <prabhak...@gmail.com> wrote:

Hi All,

1. As you all know, the DNS records for the statefulset pods using headless services are populated based on the readinessProbe statuses
   
2. But in some scenarios, the pods might want to communicate with other pods in the same statefulset to come to a ready state. This also means, the other pods initiate communications with this new pods (which are still not ready). For instances, add the node pods to the established cluster)
3. Since the DNS records would not be populated, the inter-pod communication is broken till the pods come to ready state.
4. From a non-headless service fronting the pods, it makes sense to use the readiness probes to populate the endpoints. But wondering if the same approach is required for headless services used by  statefulset pods

regards,

prpl

--
You received this message because you are subscribed to the Google Groups "Kubernetes developer/contributor discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-de...@googlegroups.com.

To post to this group, send email to kubern...@googlegroups.com.