Look at that blubber fly!

They're filming in my go to spot for a little dirt/gravel/sealed road suspension test!

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!🌈

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.

Laos was so different to what I imagined when I visited. I just expected more landscapes like northern Thailand, instead these impressively steep mountains lined the roads I travelled.

Isn't this also something that happens in the rift war books by Raymond E. Feist?

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?

I need to show people I work with how little hardware you can use to serve this much traffic. We do around 500/second but our monthly EC2 spend is horrendous for the scale of traffic we get. But rails is what it is...

I think you have it all covered, but are there ways people can contribute with time? I'm mostly k8s focused these days though.

Are you running coredns in your cluster? This sounds like a Corefile change but maybe it's just missing a service?

Pods won't have any entries in DNS aside from the pod IP addresses you've found. A Service will be in DNS and should have several entries depending on the namespace you're calling from, eg:

service-a
service-a.namespace
service-a.namespace.svc.cluster.local

I'm on mobile so haven't looked above to see if you've created a service for the pod. A service will have endpoints which are the pod ips and ports (and you can ignore endpoint slices for now)

Edit: I see coredns in there now. I'd check Corefile or the kubelet configs, seems like it can contact DNS because you're getting an NXDOMAIN response at least.