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.
Wave soldering machine - they basically suspend the whole board above a vat of solder, it bonds anywhere it can. So if they don’t need that chip on this model, it’s getting solder anyway.
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:
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!
Buildah lacks any sort of caching
… what? assuming you are using a Containerfile… what? It’s… the same as docker on layer caching. The --cache-to and --cache-from flags are particularly sweet.
Well you are not in danger of staying at that hotel now - it’s closed.
And if you were wondering, it was amazing.
We don’t have issues with unleashed dogs, or even with people not cleaning up dog crap, it’s just too much dog pee causes dead grass.
So it’s not directed at members for the states of their lawns (they are maintained by a common landscape company) it’s directed at people who have dogs who urinate - which is all of them.
It seems like all the retired people in the neighborhood have a excellent reason to be on the board but with a full time job and a kid I just don’t have the time to put towards good faith governance of the neighborhood. Maybe that’s the idea though - to get on the board and reduce their scope to paying the lawn care guys and collecting dues to pay the lawn care guys.
In an additional effort to refocus this thread to ground cover, has anyone here in the northeast US gone with a clover ground cover, rather than grass?
Interesting perspective. Other than being mad that dogs exist and inconsistent grass color I can’t imagine other slights dog owners are applying to the neighborhood. Maybe barking? But that has never really been a issue here, to my knowledge.
Paved alley, then other garages
something like this seems doable in theory but without describing the community let’s just say there is no spot to put this or any other ‘dedicated dog spot’, other than existing house’s lawns or the one 40’x40’ area which is the community green - and that totally is not going to happen.
Oh wow I read a functional ban on dogs as extreme rather than agreeable - that’s interesting.
The HOA is taking the ‘our responsibility is to keep a consistent curb-appeal’ stance so I think seemingly random houses not having grass at all may not be acceptable - though maybe that’s appropriate for the strip between the sidewalk and road.
I actually don’t know if a landlord has to do anything to keep a renter happy these days? Or if there is enough demand that they would not care? Not sure, perhaps I am approaching that question pessimistically.
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.