Moving to Google Cloud

After quite a while of procrastinating I finally took the time of setting up my production platform the way I wanted to. In the past my services and sites ran on a VPS that was managed “pet style”. I will sure miss this pet. After 6 years of faithful service it’s time to say goodbye: it’s better this way 🙂
So now all the services are running in a local(ish) datacenter in the north of the Netherlands (brand new!) and I encountered some interesting things in the new product that GCP offers; Google Filestore has a 1 TB minimum which sets the price minimum at a cool $250 dollars a month. Not so cheap when you really only need a fraction of this.
The presentation gives a visual overview of the setup and it’s versions:

  • Version 1: GKE on persistent disks and OnDemand cluster nodes: slow on restart container and expensive
  • Version 2: GKE using Buckets as central store (failed) and Preemptible nodes: not working
  • Version 3: GKE using Google FileStore (beta) and Preemtible nodes: great but expensive
  • Version 4: GKE using homegrown NFS and Preemptible nodes: fast and inexpensive!

POD stuck on terminating?

–force / –grace-timeout=0 does not work?

this worked for me:

This stackoverflow article sent me in the right direction and solved my problem: https://stackoverflow.com/questions/35453792/pods-stuck-at-terminating-status I had to type: kubectl delete pod wordpress-mysql-5f4b68789d-fsxhs --force --grace-period=0 --wait=false
kubectl edit pod wordpress-mysql-5f4b68789d-fsxhs
An editor opens with the manifest for the pod. Remove these two lines:

finalizers:

- foregroundDeletion

Saved the file and leave the editor. The pod with the ‘unknown’ state will be killed immediately and the newly spawned pod will start as usual. Shouldn’t Kubernetes take care about that? I mean: ‘force’ should tell kubernetes that I really really really want to kill a pod. Isn’t it 🙂 ? Josef

Source:  https://github.com/kubernetes/kubernetes/issues/65936

Google Filestore. Managed NFS server, nice but expensive

Even though the price Google asks for it’s new (in beta currently) service is competitive (cheaper than AWS it boasts) the smallest server you can setup is 1TB. Meaning this will set you back a cool ~$240 a month.

while impressive in speed and simplicity of setup; It’s too much for my needs (60Gb) so I’ll just give this a pass for now.