Looks more like a Bichon Frise rather than a Poodle - but probably an unnecessary distinction, as it is still cute.
Looks more like a Bichon Frise rather than a Poodle - but probably an unnecessary distinction, as it is still cute.
Just started My Little Pony: Tails of Equestria with my wife and 7yo daughter - it’s a blast!
Are you running them from your user session? If so, when you log out it will stop your processes, unless you have enabled ‘linger’ mode.
You could write a script that just restarts your container, make sure unprivileged users cannot edit it, and do one of two things:
K8s has a mild solution to chicken and egg situations for nodes - the nodes support ‘static manifests’ which can be pods they know how to bring up before ever connecting to the API server. So you could have your wireguard peer be brought up this way. Downside is while those static manifests show up in k8s APIs, they aren’t fully manageable since they are defined by files on disk.
Yea it’s very easy to learn enough to run, it has built-in service discovery and secrets now, and writing parameterized jobs feels so much nicer than a helm chart in k8s.
10/10, would orchestrate again
I use k8s at work a lot - I choose to use Nomad at home, you may want to add that to your shortlist.
I am nearly complete migrating my ceph cluster and nomad compute cluster to arm :shrug:
This - no one can agree how long a day, week, month, year etc are!
Like sure it’s 24 hours in a day but is a year 365 days? No, not technically speaking.
Time has always been really hard for programmers.
My day job is a lot of kube/openshift so nomad is refreshing. Having the template blocks are amazing and makes it so that much of what helm gave me is not required. Parameterized jobs are the best once you find a good use case for them!
In a professional setting, sometimes the cost of developing something more performant in C is not worth it. The velocity unlocked by creating systems in Go is just incredible, after your company has built everything in C[++] for decades. I find myself creating gRPC APIs in Go to solve most design challenges, because it’s stupid fast to develop and is fairly maintainable after.