3 ms·
Well, maybe it isn't _only_ what it's for, but I have thought of doing largely the same and "bundle" a bunch of assorted projects onto a single 3-node cluster,
by rcarmo 7y ago
Well, maybe it isn't _only_ what it's for, but I have thought of doing largely the same and "bundle" a bunch of assorted projects onto a single 3-node cluster, including my blog.
The only thing that's really prevented me from doing so is that I have my own micro-PaaS (https://github.com/piku https://github.com/piku) that makes it trivial to run a bunch of different apps/services on the same VPS, and the added complexity isn't really necessary.
But since I deal with k8s practically every day at customers, attrition might be compensated by not having to switch tooling.
YMMV within this sort of scope.
- wayoutthere 7y agoI mean, that’s kind of my point. It’s just not designed for that use case. Someone could build a simplified fork / derivative of Kubernetes designed for this purpose. That would be pretty rad actually, but it would cease to be Kubernetes because the complexity is the point.
- cameronbrown 7y ago> The only thing that's really prevented me from doing so is that I have my own micro-PaaS (https://github.com/piku https://github.com/piku) that makes it trivial to run a bunch of different apps/services on the same VPS, and the added complexity isn't really necessary. How does it fare in production? I've got a tiny app with two containers (a frontend an a batch job) - it seems like a decent use case.
- rcarmo 7y agoMy website (https://taoofmac.com https://taoofmac.com) is exactly that (web and batch workers) and has been running on it for almost 3 years now, but bear in mind that it does not use containers - it merely deploys relatively isolated services in virtualenvs (or equivalent). Since I use CloudFlare (hi jgrahamc!), it's been peachy.