Why is the statefulset volumeClaimTemplate phase always pending
1,437 views
Skip to first unread message
krma...@gmail.com
Jan 8, 2018, 7:59:26 PM1/8/18
to Kubernetes developer/contributor discussion
I am seeing this behavior in 1.7.3, not sure about previous releases .
Even though the statefulset pods are all ready and any rollout is complete, the phase for the underlying volumeClaimTemplate is always pending
That seems like a bug. Since that is a template , I guess it doesn’t make sense to have that field or we say hat is the aggregate status of all pvc’s . I think it makes more sense to remove his field and have the user rely on statefulset status to find the overall status of pvc pv binding and pod being ready
Thoughts ?
Even though the statefulset pods are all ready and any rollout is complete, the phase for the underlying volumeClaimTemplate is always pending
That seems like a bug. Since that is a template , I guess it doesn’t make sense to have that field or we say hat is the aggregate status of all pvc’s . I think it makes more sense to remove his field and have the user rely on statefulset status to find the overall status of pvc pv binding and pod being ready
Thoughts ?
Michelle Au
Jan 8, 2018, 8:34:05 PM1/8/18
to krma...@gmail.com, Kubernetes developer/contributor discussion
Yeah, you should look at the status of the actual PVC object created, and not the template. I imagine the field is there in the template just to reuse the PVC type definition. BTW, I don't see PVCs in the StatefulSetStatus. Only in the spec.
--
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-dev+unsubscribe@googlegroups.com.
To post to this group, send email to kubernetes-dev@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-dev/f0748144-db91-452f-a7a1-ade50ea27644%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Clayton Coleman
Jan 9, 2018, 8:36:12 AM1/9/18
to Michelle Au, krma...@gmail.com, Kubernetes developer/contributor discussion
Templates aren’t updated on other resources specs either. I would expect that field to be empty though, not pending in a template
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/CAAG1FwiHhk%2BBtaTtNK_JoUCo7xcNZsQyBV%2BEKtABY1yoA2WVCA%40mail.gmail.com.
krma...@gmail.com
Jan 9, 2018, 4:51:51 PM1/9/18
to Kubernetes developer/contributor discussion
Empty fields should probably not even show up in kubectl, i will file a issue for this.
On Tuesday, January 9, 2018 at 5:36:12 AM UTC-8, Clayton Coleman wrote:
Templates aren’t updated on other resources specs either. I would expect that field to be empty though, not pending in a template
On Jan 8, 2018, at 8:34 PM, 'Michelle Au' via Kubernetes developer/contributor discussion <kuberne...@googlegroups.com> wrote:
Yeah, you should look at the status of the actual PVC object created, and not the template. I imagine the field is there in the template just to reuse the PVC type definition. BTW, I don't see PVCs in the StatefulSetStatus. Only in the spec.
On Mon, Jan 8, 2018 at 4:59 PM, <krma...@gmail.com> wrote:
I am seeing this behavior in 1.7.3, not sure about previous releases .
Even though the statefulset pods are all ready and any rollout is complete, the phase for the underlying volumeClaimTemplate is always pending
That seems like a bug. Since that is a template , I guess it doesn’t make sense to have that field or we say hat is the aggregate status of all pvc’s . I think it makes more sense to remove his field and have the user rely on statefulset status to find the overall status of pvc pv binding and pod being ready
Thoughts ?
--
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/f0748144-db91-452f-a7a1-ade50ea27644%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages