I hate that you hate to write this, but good work doing it. I never understood why people perceive k3s as hard and then write pages of docker compose yaml instead. Admittedly my day job got me a CKA, but running k3s at home is barely a step up from docker compose.
Curious what you would use instead? I can only think of one wrong answer and that’s Jsonnet.
Correct, and since there are multiple instances I’m using a plural form, and fighting autocorrect at the same time.
My current favorite is in ruby with the unless keyword:
tax = 0.00
unless not_taxed(billing)
tax = billing.zipcode.blank? ? estimated_tax_from_ip(account) : billing.tax
tax = (tax.nil? ? 0.00 : tax)
end
To me, anything payments related you want to be really super clear as to what you’re doing because the consequences of getting it wrong are your income. Instead we have this abomination of a double negative, several turnaries, and no comments.
But there are alternatives to both CloudFlare and android, and CloudFlare has competitors with free tiers that I think are easier to use (I’m one data point)? The problem is people deciding to use CloudFlare or CloudFlare itself?
The UK has been right up there on the highest number of cameras per person in the world, this isn’t surprising. They’ve been at the forefront of this before China took the records.
It’s a shortcut for experience, but you lose a lot of the tools you get with experience. If I were early in my career I’d be very hesitant relying on it as its a fragile ecosystem right now that might disappear, in the same way that you want to avoid tying your skills to a single companies product. In my workflow it slows me down because the answers I get are often average or wrong, it’s never “I’d never thought of doing it that way!” levels of amazing.
Dream of tech bosses everywhere. Pay an intermediate dev for average level senior output.
No yaml, no helm, no operators? Using Pulumi as a layer of abstraction but not using ingress because its a layer of abstraction?
I don’t know the equivalent in GCP, but in AWS this would be treating EKS like ECS. Missing out on 90% of the benefits of kubernetes by ignoring that 90%.
But also, small company. Kubernetes is a better base to start from and expand from there.
This makes meat obelisk slices sound more appealing to me. And now I’m hungry.
From one person’s experience (mine): They don’t read CVs that closely. I’ve got a couple of 1 year jobs (not contracts) and they’re more interested in what I did rather than why so short. If they ask I tell them it’s because I didn’t like the position but gave it a go for a year. I also have a 2 year gap in employment none of them are interested in for 4 jobs now, they don’t even spot the missing years and I’ve had to point it out in interviews because it’s a story of how I deal with big tasks.
If they are that petty that they’ll pass me over because of something like that then that employers policies would raise more flags than I’d want to deal with anyway.
When hiring you have hundreds of CVs pass by, I’m looking for experience, we’ll sort out these other details in the interview.
Caveat: I am older now, more senior but never had issues finding work.
Im pretty senior now, you’d pass me by and the most valuable thing I’d do is to reduce that learning time.
I don’t know what you do, but in my IT jobs I’ve seen long onboarding times are due companies not focusing on their product, eg: a finance company writing their own authentication system, or maintaining someone’s vanity project who has long since departed. Get rid of that and you can bring people in off the street.
I probably had, but I also probably erased it with some beer later. These days I only know and retain YAML.
It’s Always Sunny had an episode like this. Now I know it’s based on a real story. How rare.
Is Les Claypool still alive in that world where Flea is the greatest?
Ha. I guess I rewrote my own memory.
Edit: complete fabrication be here.
The “do horrible thing to save someone” story, yeah, maybe.
But the pig thing had been going around for years about the then/former prime minister. Some kind of hazing at eton or wherever those posh folks go. The episode was just a reference to that.
Safest way to ensure I WILL eat this meme: tell me not to.
Yeah for reference I’d probably never run the full open source Kubernetes distribution unless I had to, and that would mean having access to millions of dollars of hardware in a datacenter.
K3s is a lightweight Kuberbetes distribution that implements the full Kuberbetes API (full-ish? Maybe?). It’s super easy to run on Linux, I run a 3 node cluster with GPUs at home. Its only real downside is the backend is a single point of failure, but that’s ok for me cause it’s run from my storage node with all the disks, so if that disappears I have bigger problems.
There are others like microk8s which can handle control plane failures, but it’s for that reason that I also dislike it - they wrote their own distributed sqlite instance and it failed on me, a story for another time.
Minikube can run on your desktop, it’s also an option.
But if you have docker desktop, you also have a built in Kuberbetes API server too, just have to enable it with one checkbox (not a full API server, but good enough for installing helm charts).
Kind is a docker based Kubernetes server but I think that’s in the realm of testing not running. I believe K0s is in this camp too but could be wrong.
At work the daily driver will be one of EKS, GKE, AKS, or whichever cloud providers implementation. They’re effectively free and a loss leader because you’ll pay for instances anyway (at least on EKS, I’m most familiar with that one).
But if you’re interested in learning, start with docker desktops k8s API, or minikube, or k3s if you have a Linux host or raspberry Pi lying around.
🌈The more you know!🌈