I'm with Tim. Without a non machine specific chroot you end up with chaos.
-
-
More specifically: the cluster/node ops and app ops story is super tightly coupled.
1 reply 0 retweets 0 likes -
See https://mesosphere.github.io/marathon/docs/application-basics.html … -- Marathon represents the most common deploy-time packaging method in Mesos land.
1 reply 0 retweets 0 likes -
Yup. All examples there make huge assumptions on node config. Reference python with no indication of which python. Tight coupling.
1 reply 0 retweets 1 like -
I'm not saying this is the right path, but it is what many people went with and got "locked-in" to well (maybe 2 yr?) before K8s came out.
1 reply 0 retweets 1 like -
But container images are the WAY OUT of that quagmire
3 replies 0 retweets 7 likes -
I agree containers are the way out but running binary is the way in to using k8s instead of custom solutions.
2 replies 0 retweets 2 likes -
Lots have solved the problem (not in great ways) of how to get bin + deps onto nodes to run
1 reply 0 retweets 1 like -
But that tightly couples the node config and management with workload description. Lots of disadvantages there.
3 replies 0 retweets 3 likes -
Even Google is moving away from this model
1 reply 1 retweet 8 likes
Serverless makes it easier to deploy just apps, if that's what people want.https://github.com/kubeless/kubeless/issues/148#issuecomment-302665766 …
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.