10 ms·

Huh? Why would you say something like this? What about StatefulSets and all the related resources?

cookiecaper 10y ago
These are marked beta, and they don't address all of the needs of stateful applications. This blog post [0] from the official k8s blog covers many of the caveats well, and basically describes databases as the anti-use case with statements like: >What is the benefit you hope to gain by running your application in a StatefulSet? [...] If you have a few instances of your storage application, and they are successfully meeting the demands of your organization, and those demands are not rapidly increasing, you’re already at a local optimum. [0] http://blog.kubernetes.io/2016/12/statefulset-run-scale-stateful-applications-in-kubernetes.html http://blog.kubernetes.io/2016/12/statefulset-run-scale-stat...
- linkmotif 10y ago
  They've been out of beta a few months now and are well supported in GCE. You can't have an application without state, and the k8s team recognizes this. Anyway, OP is about MySQL I guess :)
  - cookiecaper 10y ago
    They're not out of beta. See this comment [0] on the GitHub issue titled "StatefulSets", which was made on February 3, 2017, and says: >This is beta. May have minor changes in 1.6 but not going GA. The latest release of k8s is 1.6, made on March 28, 2017, about two weeks ago. [1] Furthermore, the issue still bears the "stage/beta" tag. [0] https://github.com/kubernetes/features/issues/137#issuecomment-277368629 https://github.com/kubernetes/features/issues/137#issuecomme... [1] https://github.com/kubernetes/kubernetes/releases/tag/v1.6.0 https://github.com/kubernetes/kubernetes/releases/tag/v1.6.0
    - linkmotif 10y ago
      Oh my bad, then. Thanks for the links.
- thockingoog 10y ago
  Please remember that Kubernetes itself is literally less than 2 years GA. Stateful is hard. It wasn't the first thing we tackled. It's in progress now, and feedback so far is pretty good. That may not be enough for you yet, and that's OK. Check back in 6 months and see how it is progressing.

These are marked beta, and they don't address all of the needs of stateful applications. This blog post [0] from the official k8s blog covers many of the caveats well, and basically describes databases as the anti-use case with statements like: >What is the benefit you hope to gain by running your application in a StatefulSet? [...] If you have a few instances of your storage application, and they are successfully meeting the demands of your organization, and those demands are not rapidly increasing, you’re already at a local optimum. [0] http://blog.kubernetes.io/2016/12/statefulset-run-scale-stateful-applications-in-kubernetes.html http://blog.kubernetes.io/2016/12/statefulset-run-scale-stat...

linkmotif 10y ago
They've been out of beta a few months now and are well supported in GCE. You can't have an application without state, and the k8s team recognizes this. Anyway, OP is about MySQL I guess :)
- cookiecaper 10y ago
  They're not out of beta. See this comment [0] on the GitHub issue titled "StatefulSets", which was made on February 3, 2017, and says: >This is beta. May have minor changes in 1.6 but not going GA. The latest release of k8s is 1.6, made on March 28, 2017, about two weeks ago. [1] Furthermore, the issue still bears the "stage/beta" tag. [0] https://github.com/kubernetes/features/issues/137#issuecomment-277368629 https://github.com/kubernetes/features/issues/137#issuecomme... [1] https://github.com/kubernetes/kubernetes/releases/tag/v1.6.0 https://github.com/kubernetes/kubernetes/releases/tag/v1.6.0
  - linkmotif 10y ago
    Oh my bad, then. Thanks for the links.
thockingoog 10y ago
Please remember that Kubernetes itself is literally less than 2 years GA. Stateful is hard. It wasn't the first thing we tackled. It's in progress now, and feedback so far is pretty good. That may not be enough for you yet, and that's OK. Check back in 6 months and see how it is progressing.