Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Claude Code for Infrastructure

fluid.sh

Post reply on HN
Print view View original

11–20 of 190 posts

Re: Claude Code for Infrastructure

#11

Post by redfloatplane »

Clever solution. I think ops (like this) and observability will be pretty hot markets for a while soon. The code is quite cheap now, but actually running it and keeping it running still requires some amount of background. I've had a number of acquaintances ask me how they can get their vibe coded app available for others to use.

I really like this idea. I do a lot of kubernetes ops with workloads I'm unfamiliar with (and not directly responsible for) and often give claude read access in order to help me debug things, including with things like a grafana skill in order to access the same monitoring tools humans have. It's saved me dozens of hours in the last months - and my job is significantly less frustrating now.

Your method of creating ansible playbooks makes _tons_ of sense for this kind of work. I typically create documentation (with claude) for things after I've worked through them (with claude) but playbooks is a very, very clever move.

I would say something similar but as an auditable, controllable kubernetes operator would be pretty welcome.

Re: Claude Code for Infrastructure

#13

Post by jondwillis »

redrove wrote: post #6
aspectrr wrote: post #2

Hey HN, My name is Collin and I'm working on fluid.sh ( https://fluid.sh ) the Claude Code for Infrastructure. What does that mean? Fluid is a terminal agent that do work on production infrastructure like VMs/K8s cluster/etc. by making sandbox clones of the infrastructure for AI agents to work on, allowing the agents to run commands, test connections, edit files, and then generate Infra-as-code like an Ansible Playbo…

So how is this different from deploying claude code on a VM and letting it run? You can sandbox it in any of the dozen ways already available. What’s the differentiator?

One allows middleman rent-seeking and the other does not so much.

Re: Claude Code for Infrastructure

#14

Post by aabajian »

falloutx wrote: post #9

All these tools to build something, but nothing to build. I feel like I am part of a Pyramid Scheme where every product is about building something else, but nothing reaches the end user. Note: nothing against fluid.sh, I am struggling to figure out something to build.

That is the problem with software developers with expertise in software, but no deep domain knowledge outside the CS world.

Re: Claude Code for Infrastructure

#16

Post by levkk »

So... I already tell Claude Code to do this. Just run kubectl for me please and figure out why my helm chart is broken.

Scary? A little but it's doing great. Not entirely sure why a specialized tool is needed when the general purpose CLI is working.

Re: Claude Code for Infrastructure

#17

Post by mindwok »

falloutx wrote: post #9

All these tools to build something, but nothing to build. I feel like I am part of a Pyramid Scheme where every product is about building something else, but nothing reaches the end user. Note: nothing against fluid.sh, I am struggling to figure out something to build.

Speak for yourself. I’ve been using Claude Code to build lots of customer facing things.

Re: Claude Code for Infrastructure

#18

Post by redfloatplane »

levkk wrote: post #16

So... I already tell Claude Code to do this. Just run kubectl for me please and figure out why my helm chart is broken. Scary? A little but it's doing great. Not entirely sure why a specialized tool is needed when the general purpose CLI is working.

Yeah. The times I have let claude off the read-only leash, it's gone fine for me too (with stern warnings not to do anything stupid, and a close eye). But that's not really solving the same problem as this project, I guess. From what I can see this is using a safer and more reproducible method (and not k8s native, so it feels a little foreign to me).

Re: Claude Code for Infrastructure

#19

Post by giancarlostoro »

redfloatplane wrote: post #18
levkk wrote: post #16

So... I already tell Claude Code to do this. Just run kubectl for me please and figure out why my helm chart is broken. Scary? A little but it's doing great. Not entirely sure why a specialized tool is needed when the general purpose CLI is working.

Yeah. The times I have let claude off the read-only leash, it's gone fine for me too (with stern warnings not to do anything stupid, and a close eye). But that's not really solving the same problem as this project, I guess. From what I can see this is using a safer and more reproducible method (and not k8s native, so it feels a little foreign to me).

In Zed I just have it auto approve everything, macOS will scream if "Zed" tries to escape the folder its in anyway.

Re: Claude Code for Infrastructure

#20

Post by xyzzy123 »

lijok wrote: post #4

FUCK NO. Who in their right mind would let an LLM connect to prod?

Many places have "dev", "test" "prod"... but IMHO you need "sandpit" as well.

From an ops point of view as orgs get big enough, dev wraps around to being prod-like... in the sense that it has the property that there's going to be a lot of annoyed people whose time you're wasting if you break things.

You can take the approach of having more guard rails and controls to stop people breaking things but personally I prefer the "sandpit" approach, where you have accounts / environments where anything goes. Like, if anyone is allowed to complain it's broken, it's not sandpit anymore. That makes them an ok place to let agents loose for "whole system" work.

I see tools like this as a sort of alternative / workaround.

Post reply on HN