fideloper
Joined 14 years ago
Karma
2,359
Submissions
535
Member since
Jun 26
Infra at Laravel Cloud. Creator cloudcasts.io, chipperci.com, serversforhackers.com
View on Hacker NewsRecent submissions
Comment · 2 months ago
this all closed source?
Comment · 9 months ago
i believe the .sprite dir has some stuff to help claude answer those questions. haven’t done it myself but my friend said he was able to get claude to set it all up for him (yolo mode helps) including connecting to github.
Comment · 1 year ago
i grew up really close to that
Comment · 1 year ago
I might just be too dumb to read even an abstract, but it sounds like they said "meh idk, no strong evidence"
(also curious if they'd call going hard on crypto / options "gambling" or not :P, which might be more about how hard it is to get ahead in todays economy than playing games as a kid, but that point is a very hard digression from what we're talking about here).
Comment · 1 year ago
"Low maintenance", welp.
I suppose that's true in one sense - in that I'm using EKS heavily, and don't maintain cluster health myself (other than all the creative ways I find to fuck up a node). And perhaps in another sense: It'll try its hardest to run some containers so matter how many times I make it OOMkill itself.
Buttttttttt Kubernetes is almost pure maintenance in reality. Don't get me wrong, it's amazing to just submit some yaml and get my software out into the world. But the trade off is pure maintenance.
The workflows to setup a cluster, decide which chicken-egg trade-off you want to get ArgoCD running, register other clusters if you're doing a hub-and-spoke model ... is just, like, one single act in the circus.
Then there's installing all the operators of choice from https://landscape.cncf.io/. I mean that page is a meme, but how many of us run k8s clusters without at least 30 pods running "ancillary" tooling? (Is "ancillary" the right word? It's stuff we need, but it's not our primary workloads).
A repeat circus is spending hours figuring out just the right values.yaml (or, more likely, hours templating it, since we're ArgoCD'ing it all, right?)
> As an side, I once spent HORUS figuring out to (incorrectly) pass boolean values around from a Secrets Manager Secret, to a k8s secret - via External Secrets, another operator! - to an ArgoCD ApplicationSet definition, to another values.yaml file.
And then you have to operationalize updating your clusters - and all the operators you installed/painstakingly configured. Given the pace of releases, this is literally, pure maintenance that is always present.
Finally, if you're autoscaling (Karpenter in our case), there's a whole other act in the circus (wait, am I still using that analogy?) of replacing your nodes "often" without downtime, which gets fun in a myriad of interesting ways (running apps with state is fun in kubernetes!)
So anyway, there's my rant. Low fucking maintenance!
Comment · 1 year ago
I don't think AI is central to this article at all (altho, sure, it's mentioned)
Comment · 1 year ago
I think the idea is your phone will do that for you via carplay (etc)
Comment · 1 year ago
“just add more complexity”
Comment · 1 year ago
May I recommend a follow up fun Garfield themed thing: /r/imsorryjon (research its history, it's kinda fun)
And if you like "garfield minus garfield" then perhaps I can also introduce you to Chief O'Brien at Work https://chiefobrienatwork.com/
Comment · 1 year ago
That feature exists on cloudflare outside of using CF workers or their own compute stuff. It's part of their WAF featureset.
Comment · 1 year ago
Wait, how do you run firecracker VMs in containers? The networking part of firecracker has been the most painful for me, I’d love to know more.
Comment · 2 years ago
they also provide certs for mTLS between cloudflare and your origin, which you can layer in along with IP restrictions
(the term they use is “authenticated origin pull”)
Comment · 2 years ago
Agree, was disappointed there was no easter egg here.
Comment · 2 years ago
I use it to power CI builds (a lot of them!) and have extremely little issue with it.
Basically I’m just using the API to spin up machines, which do some work and shut down. There’s some extra machines per build job, like database containers or a headless browser for testing. Pretty smooth in my experience.
I think the only occasional issue I hit is the internal DNS being a few seconds behind reality.