6 ms·
When picking preemptive machines for this demo project is the intention here to simply save money for a pet project? I guess my main question is would anybody
by deckarep 8y ago
When picking preemptive machines for this demo project is the intention here to simply save money for a pet project?
I guess my main question is would anybody actually use preemptive for k8s knowing that if a worker node gets reaped k8s will magically route only to healthy nodes while the preempted instance replacement is standing up?
- tmaier 8y agoSure! First of all, GK3 would create new nodes when one of them gets killed. Second, builidng “cloud-native” applications means to build stateless applications, e.g. using 12-factor. So it does not really matter if your application gets killed, restarted or horizontally scaled. For databases, i always recommend to use a PaaS offering to have an easy and worry-free life
- donmcronald 8y agoWhat if all 3 nodes get killed at the same time? Can you use the always free instance + 2 preemptible instances?
- DuskStar 8y agoYou can set GKE up to use multiple groups of nodes, yes. In this case you'd want to configure one group with a single non-preemptible micro node, and a second with two preemptible micro nodes. It's not something I'd really worry about for a hobby project though.
- halbritt 8y agoI use preemptible nodes extensively in my production environment.
- maktouch 8y agoWe pretty much run 98% of our stuff in preemptibles. It's a free chaos monkey that makes your stuff cheaper too! Just make sure your app has proper probes, and make sure the probes returns 500 when the process receives a sigterm, and it should be invisible to you.
- bullen 8y agoThis article should be renamed "Google now has expensive feature that reboots your instances every 24 hours". Server-less will be remembered as the most embarrassing thing humans have ever invented.