r/devops

I see so many cool demos of agents writing code, deploying stuff, resolving incidents. Every week there's a new one that looks incredible.

Then I talk to the eng orgs actually trying to do this at scale and it's a completely different story. The AI part works fine. What breaks is everything around it.

I wrote up 7 specific debts I keep seeing that block orgs from going beyond the demo phase.

Disclaimer: I'm the CEO of port.io so take that into account. This comes from my newsletter and what I see talking to eng teams every week.

<Totally not AI generated problem statement that actually just exposes that OP has 0 clue about how anything works>

<Github link 80% of the time. Usually created 1 or 2 days ago. Completely out of whack when compared to OP's other public repo code which are usually named ~"python||typescript testing". Only shows OP as contributor cause they make the repo with AI first then delete and copy/paste/push >

<Generic asking for feedback section and statement that there is a paid version but you dont need to use it at first>

All credit to /u/Arucious for this one lmao

If you could start on a green field, which ingress architecture would you go with? Here are a few constraints:

• Single region deployment
• No legacy Ingress API
• Preferably WAF builtin

Here are some options I considered so far:

• Option 1: Azure Application Gateway for Containers
• Option 2: Envoy Gateway
• Option 3: Traefik

Azure Application Gateway for Containers is a new offering from Azure that uses Gateway API. Would be interesting to hear any experience from people who are actually running it in production.

If you have any good references/comparisons, would be curious the read them.

Bear with me here. I'm thinking about having an openclaw agent that devs can interact with when they want to add a new app on our EKS cluster. For now it would be for the nonprod cluster only.

Say they can interact with the agent through slack. They tell the agent about what their app will need. Like open port 8080, make a pvc, make a configmap with those values. Then the agent creates the new app from an helm template and would also create the cicd pipeline from a template. The agent could open a Jira ticket a pr for us to review before applying the change. It could also document the app in confluence. I don't see why this would not work. And we make sure the agent only has limited credentials and network accesses

When we want to deploy the app on the prod cluster we could do it ourselves for now.

I see that it isn't very popular these days. I'm wondering what's the "meta" of automation platform/tools nowadays that worth checking out?