3 ms·
> Also, we run a VPC-only K3s node for some simple internal tools that works great as well. We do exactly the same thing! We have a one-node k8s for all these
by dvcrn 6y ago
> Also, we run a VPC-only K3s node for some simple internal tools that works great as well.
We do exactly the same thing! We have a one-node k8s for all these dev things that just works. Everything is containerized for local dev anyway so moving it to k8s was just writing the deployment manifest.
On heroku, all of these would be separate dynos (or one glued-together dyno that does everything). On a self-hosted VM we'd have to deal with managing that.
I liked this approach so much that I now have a small 1-node personal cluster that hosts all of my private hobby projects that aren't ready for prime time yet, that were on heroku previously. Costs me only $10 + (persistent storage + IP address if needed)
- meigwilym 6y agoYou really should write an article detailing how all this is set up. It sounds fascinating.
- dfee 6y agoI feel like I’m witnessing two co-founding colleagues - who sit by each other day in and day out - discover the other’s persona on HackerNews. Sure, maybe you two (@dvcrn and @arcticfox) don’t work together and don’t know each other, but it’s definitely more entertaining imagining the scenario above.
- charlieflowers 6y ago“If you like pina coladas...”
- KineticLensman 6y agohttps://en.wikipedia.org/wiki/Escape_(The_Piña_Colada_Song) https://en.wikipedia.org/wiki/Escape_(The_Piña_Colada_Song)