Now install tools that are only available as github released binaries. And ensure that hashes match for that. Maybe install a tool that needs to be compiled.
Now install tools that are only available as github released binaries. And ensure that hashes match for that. Maybe install a tool that needs to be compiled.
What if, get this, we put the bash scripts in yaml. And then put it in kubernetes.
And what is the token in the link?
Define production lol. I’ve used it for a CI cluster for a few years. Have had to recreate it a few times due to database corruption (despite using etcd across 3 nodes).
Honestly Rancher management is more of a pain than manually managing via ansible or something. And swapping to CRI-O backend instead of containerd js a huge pain for Rancher/RKE2, but pretty easy with k3s.
You know what’s cool fanservice? Andor using a Bryar Pistol. You know what’s not cool fanservice? Seeing the same 10 characters again and again and again. Seeing the same bar in an enormous galaxy.
Kenobi at the very least added some linking character development between ROTS and ANH, despite how awkward some of it was. So that I’m OK with.
Consider that a ‘username+password’ is much harder to ‘revoke’ individually. As in, you can have 3-4 API keys in use, and can revoke any one of them without having to change a password.
You can also change password independently of the keys, or have it linked so keys are revoked on a password change. It also allows traceability as to where accesses are coming from (auditability). If everything is using the same client-id+secret (or usn/pwd), you don’t know which ‘client’ is doing what.
It’s the sort of thing that makes me really, really sad for the people working there. That crazy breakneck pace cannot be good for mental health.
Did you only make it past the first paragraph? Cause you missed the years of scummy shit they’ve done, completely unrelated to politics.
I’d agree more if most docker stuff didn’t depend on running as root.