If you use StatefulSet, you may experience the following symptoms (reported in #48327 <https://github.com/kubernetes/kubernetes/issues/48327>) after upgrading to v1.7.x:
* StatefulSet emits errors (seen in `kubectl describe`) containing "*Forbidden: pod updates may not change fields other than...*". * StatefulSet Pod DNS entries stop resolving. If this happens, you will need to delete each affected Pod and allow the StatefulSet to recreate it, since the relevant fields (spec.hostname and spec.subdomain) are immutable. If you haven't upgraded to v1.7 yet, you can use the following process to minimize disruption: *1) Upgrade first to the latest v1.6.x (at least v1.6.9).* In this version, StatefulSet creates Pods that will keep working on v1.7.x. If you start a new cluster on v1.6.9, or you did not have any StatefulSets created before v1.6.9, no further action is required. *2) Perform a manual rolling update on existing StatefulSets* by deleting Pods one at a time and letting the v1.6.9 StatefulSet recreate them. *3) Upgrade to the latest v1.7.x (at least v1.7.5).* -- 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.
