git rebase and chaos

Added some hard gated commit checks in pipeline which requires editing commit message in repo and it's been absolute cinema since (even after providing a step by step guideline)

the dev who talked louder in weekly syncup => just lost it because it's too much to handle
the principal engineer => performed rebase which added more wrong commits
the newbie joining => setup a KT meeting on Saturday for rebase


https://redd.it/1mr6obm
@r_devops

Should I quit my new job

Hi there, as the title says, I am contemplating quitting my new job because my expectations is different from reality. I was very open during my interview that I do not have devops experience (i have only work with Azure DevOps with guidancefrom automationteam), I only have experience working with managing azure resources in my previous job but now that I have the job I am being told I'll work with all this technologies that I've never work with such as Github action, terraform, kubernetes and other.

I started 3 weeks ago and I am already thinking of quitting, I do not have any direct senior in DevOps path within our department, I only have one from another department and he's basically handling stuffs to me to work on which I have no idea how to get done.

I appreciate all advise

https://redd.it/1mr9xf7
@r_devops

How to deploy safer

I'm building out something for the first time myself, and from my previous experience (and even more-so now building it myself), I haven't found a great solution better than "deploy to staging and see what happens".

There are terraform tests, and some basic linters, but I want a higher guarantee that I'm not overwhelming a service or killing my DB because of some bad config I set. Anyone heard of anything which can do that?

https://redd.it/1mrba7i
@r_devops

New devs - Zero imposter syndrome

What has happened to the dev community? The "new gen devs" are complete divas with zero interest in learning. What they know or learn by themselves is "enough" and seniors are wrong. The front end should be as advanced as possible with a node_modules directory larger than the entire internet back in 1995. If it gets too advanced, they just "vibe it". When I landed my first job, I had major issues with the imposter syndrome.

I had junior front end devs talking about backend stuff I were not familiar with (WordPress agency, I had not yet understood everything with their hooks). I took assistance from the developer. But today? I get runned over by junior front end developers. I can literally tell him exactly how his project will crash and all I get is "thats not how it works"

This is not a rant, I wanna know how and why all of this went sideways. Anyone else experiencing this? I never thought I would actually wanna slap a co-worker. I mean, I cant be the only one?

https://redd.it/1mrdkbe
@r_devops

Automating upgrades for helm andEKS resources

We're currently using terraform to manage our EKS cluster but having to meet a new requirement where we upgrade within 5 days of a release for all resources in our kubernetes environments. We deploy things like LGTM, CNPG, OTEL operator, kyverno, and other similar helm managed products. Is anyone automating their upgrades for at least bug fix versions for products like this? If so what are you using to do it

https://redd.it/1mresbh
@r_devops

Git Rebase - Explained Like You’re New to Git`

If `git merge` feels messy and your history looks like spaghetti, `git rebase` might be what you need.

In this post, I explain rebase in **plain English** with:

* A simple everyday analogy
* Step-by-step example
* When to use it (and when NOT to)

Perfect if you’ve been told “just rebase before your PR” but never really understood what’s happening.


Read it here -> [https://medium.com/stackademic/git-rebase-explained-like-youre-new-to-git-263c19fa86ec?sk=2f9110eff1239c5053f2f8ae3c5fe21e](https://medium.com/stackademic/git-rebase-explained-like-youre-new-to-git-263c19fa86ec?sk=2f9110eff1239c5053f2f8ae3c5fe21e)

https://redd.it/1mroew6
@r_devops

Are Deep Work and Operations work incompatible?

One thing I’ve had trouble with in DevOps is context switching between last minute and high priority tasks. When you spend most of your day jumping from issue to issue, it leaves little space for the kind of focused work that reduces toil (like automation or system design).

I recently wrote about applying Cal Newport’s Deep Work ideas to DevOps. Things like timeboxing, reducing distractions from IM/email, or even experimenting with “mini think weeks” while you are not on call.

Curious, how do you make time for deeper, proactive work in such an interruption-heavy field?

(Link to full post if people want a read: https://medium.com/@timlittle88/beyond-the-pager-using-deep-work-to-reduce-devops-toil-0e8488d0628f)

https://redd.it/1mrq615
@r_devops

Workload Identity Federation Explained with a School Trip Analogy (2-min video)

Static keys are still everywhere — hardcoded in configs, repos, and scripts — and they’re a huge security liability.

I put together a 2-minute video explaining Workload Identity Federation (WIF) using a simple school trip analogy (students, teachers, buses, and wristbands).

🔑 Covers:

Why static keys are risky
How WIF works step by step
Benefits of short-lived tokens
When (and when not) to use it

YouTube video: https://youtu.be/UZa5LWndb8k
Read more at: https://medium.com/@mmk4mmk.mrani/how-my-kids-school-trip-helped-me-understand-workload-identity-federation-f680a2f4672b

Curious — are you using WIF in your workloads yet? If not, what’s holding you back?

https://redd.it/1mrvas0
@r_devops

Would you use a completely local LLM-powered terminal assistant for your DevOps workflows?

Hey r/devops!

I'm working on a terminal tool idea and wanted to get your thoughts before diving deep into development.

The Problem

We've all been there at 2AM:

* "What's the exact jq syntax to parse this nested JSON from the API response?"
* "I need that awk command to extract the 5xx errors from nginx logs... again"
* "Which kubectl flag shows pod resource limits vs requests?"
* "How do I get Docker to show just the container IDs that match this pattern?"
* "That one-liner to find all processes listening on ports... was it netstat or ss?"

Even senior devs know the tools exist but forget the exact syntax. Junior devs are constantly context-switching between docs and terminal.

The Solution I'm Building

A terminal RAG system that:

* Takes natural language input → searches vector DB of commands → executes the right one
* Vector DB of common DevOps commands - semantic search matches your query to pre-stored command patterns
* 100% local processing - no production data sent anywhere (CISO-approved!)
* Zero external API calls - works in air-gapped environments, no Claude Code or GitHub Copilot needed

# Example workflows (from simple to "oh god please work"):

**Simple stuff:**

$ ask "make a new folder called backup"
# Finds: mkdir backup


$ ask "show me running processes"
# Finds: ps aux


**Getting spicy:**

$ ask "find files bigger than 100MB modified in the last week"
# Finds: find . -type f -size +100M -mtime -7 -exec ls -lh {} \;


$ ask "show me pods using more than 500MB memory"
# Finds: kubectl top pods --sort-by=memory | awk '$3 > 500 {print $0}'


**The "please just work I'm dying" level:**

$ ask "which container is eating memory and crashing nodes"
# Finds: docker stats --format "table {{.Container}}\t{{.MemUsage}}\t{{.MemPerc}}" --no-stream | sort -k3 -nr
# Shows: nginx-prod 1.8GB / 2GB (90%) ← Found your problem


$ ask "parse nginx logs for 5xx errors in the last hour with client IPs"
# Finds: awk -v hour=$(date -d '1 hour ago' '+%d/%b/%Y:%H') '$4 ~ hour && $9 ~ /^5/ {print $1, $9, $7}' /var/log/nginx/access.log


Why This vs. Claude Code/GitHub Copilot?

* Actually local - works in secure/air-gapped environments where external AI tools are blocked
* DevOps-focused - curated for infrastructure commands, not general coding
* No subscription costs - no per-seat licensing for your team
* Instant response - pre-computed embeddings, no API round trips
* Your data stays put - server names, configs, internal commands never leave your network

The Tech (RAG-based)

Current MVP Plan:

* Vector database of common DevOps commands and patterns
* Semantic search to match natural language → command mappings
* Local execution with safety checks

Future: Custom local LLM trained on DevOps patterns (separate enterprise offering)

Questions for you:

1. Junior/Mid-level devs: What's the command syntax you always have to look up?
2. Senior devs: Even if you know the commands, would you use this for speed during incidents?
3. Enterprise folks: Would your security team approve a local-only tool vs. Claude Code/Copilot?
4. Everyone: How often do you find yourself thinking "I know there's a command for this but..." during time-sensitive situations?

I'm especially curious - would experienced devs use this for speed/convenience, or is this more valuable for junior devs learning the ropes?

Any feedback, roasting, or "shut up and take my money" reactions welcome!

TL;DR: Building a local RAG system that converts "which container is crashing my nodes" into the exact docker/kubectl commands you need, without sending any data to external APIs. No more 3AM Stack Overflow hunting during incidents.

https://redd.it/1mrxdyl
@r_devops

Scaling reads and writes in an application

I wrote a 2-part series breaking down something we often take for granted in system design - scaling reads vs writes.

Part 1 covers practical ways to scale reads: caching, indexing, replicas, CDNs, and other tricks we’re usually expected to know (especially in interviews).
Part 2 goes into the messy stuff — batching, queues, sharding, and why writes are often the real bottleneck.

Both parts are hands-on and dev-friendly, with examples and real-world context. Hope it helps someone facing the same pain points.

👉 Part 1: https://medium.com/stackademic/from-interview-questions-to-real-world-fixes-techniques-to-scale-reads-2f3b534400b0?sk=7698e78e3a0953ee980e2e340b0ba86a
👉 Part 2: https://medium.com/stackademic/scaling-writes-in-system-design-the-stuff-that-can-break-your-application-67f7990579b9?sk=e74ea8b5a281bf34b8965015849c812d

Would love to hear how you’ve handled high write loads or tricky read paths in your own projects.

https://redd.it/1mrz6dv
@r_devops

Linux

Hey! I've started learning the DevOps workflow and tools. As the foundational tool, I am learning Linux. I wanted to know where can i practice those commands other than my local system (wsl) so that i get proper hands-on practice? Like some assignments?

https://redd.it/1ms1ec1
@r_devops

Looking for a design partner to run a Finops pilot to cut your AWS cost by 30 percent

I have built a POC for cutting cloud cost (in AWS) by 30 percent. How do find a design partner to run this POC in a real environment to demonstrate it works? Anyone open to try this for your AWS account? or even happy to share what i have built and get your thoughts.

https://redd.it/1ms4hn1
@r_devops

Need a DevOps mentor.

Hey everyone,

I’m currently on my DevOps journey and looking for a mentor who can help guide me as I grow in this field. I’ve been working on building skills in areas like CI/CD, cloud platforms (AWS/Azure/GCP), containerization (Docker, Kubernetes), and Infrastructure as Code, but I often feel like I’m missing the “big picture” of how all the pieces fit together in real-world environments.

I’d love to connect with someone experienced in DevOps/SRE who can:

Share insights on best practices

Help me structure my learning roadmap

Give career advice (what skills/tools to prioritize)

Maybe even do mock interviews or review my projects/resume


I’m not looking for free consulting—more like a mentor/mentee relationship where I can learn from your experience, and I’ll put in the effort on my side.

If you’ve been in the industry for a while and wouldn’t mind helping someone new navigate this path, I’d be super grateful. Even a few occasional chats/check-ins would mean a lot.

Thanks in advance!

https://redd.it/1ms5cql
@r_devops

Need advice

Hi Everyone, I'm 24 M working as an IAM analyst with 1.8 years of experience and i am in a project where i use Azure entra ID. I'm thinking of changing my role to Cloud engineer or DevOps engineer as I really like Cloud computing and i have done projects in kubernetes and certifications regarding Azure cloud. But sometimes i think even if i make projects on cloud i won't have real production expertise and why would any company hire me on basis of certifications and personal projects. Please guide me if this switch will be possible or should i stick with IAM only.

https://redd.it/1ms5n98
@r_devops

LambdaTest is hosting TestMu, the world’s biggest virtual software testing conference featuring 80+ powerhouse speakers from Google, Amazon, Accenture, and beyond.

Created by the community, for the community, it’s a space to grow, connect and lead together. We’ll have deep-dive sessions on emerging trends in engineering, DevOps and Agentic and AI powered Software Testing.

3 days of power-packed sessions with 80+ speakers and 60+ sessions, you will also get an opportunity to connect and engage with 50k+ attendees from 120+ countries.

You’ll gain cutting-edge insights from world-class speakers on AI, automation, and the future of testing and get a chance to explore next-gen tools, frameworks, and strategies to transform your testing workflows and accelerate innovation.

All registered attendees will have access to the recordings as well.

Showcase your skills in live challenges and quizzes for a chance to win prizes worth up to $10,000 and gain global recognition.

https://redd.it/1mscsvd
@r_devops

I built an open source AI workflow orchestrator with GitOps-friendly YAML DSL

Hey DevOps folks, I wanted to share an open source (Apache 2.0) project that bridges the gap between AI capabilities and DevOps practices.

Lacquer (https://github.com/lacquerai/lacquer) is an AI orchestration engine that brings Infrastructure-as-Code principles to AI workflows. Define complex AI pipelines in YAML, version control them alongside your infrastructure code, test in dev environments, and deploy to production with confidence. Here's simple example that summarizes a given pr:

version: "1.0"

agents:
  code_reviewer:
    provider: openai
    model: gpt-4
    temperature: 0.3
    system_prompt: You are an expert code reviewer who analyses pull requests.

inputs:
  pr_number:
    type: integer
    description: Pull request number to review
    required: true

workflow:
  steps:
    - id: fetch_pr
      run: node scripts/fetch_pr.js
      with:
        pr_number: ${{ inputs.pr_number }}

    - id: analyze_changes
      agent: code_reviewer
      prompt: |
        Please analyze this pull request and help me review it:
        
        ${{ steps.fetch_pr.outputs.diff }}
        
        Please provide:
        1. **Summary**: What does this PR do in simple terms?
        2. **Key Changes**: What are the main files/functions modified?
        3. **Potential Concerns**: Any issues or risks to be aware of?
        
        Keep explanations clear and accessible.

  outputs:
    pr_analysis: "${{ steps.analyze_changes.output }}"

I built this because I was tired of AI tools that don't fit into modern DevOps workflows - no version control, no reproducible deployments, no proper testing environments. Lacquer changes that by treating AI workflows as infrastructure:

- GitOps Ready: All workflows are YAML files that live in your repos
- CI/CD Integration: Run as part of your existing pipelines (Jenkins, GitLab CI, GitHub Actions, etc.)
- Single Binary Deployment: Ships as one Go binary - no complex dependencies or container orchestration needed
- Environment Parity: Test locally, stage in dev, deploy to prod with the same configuration
- Observability Built-in: Structured logging and metrics for monitoring AI operations

Perfect for automating incident response, PR reviews, documentation generation, or any repetitive task that needs intelligence. You can trigger workflows via CLI, REST API, or embed directly into your automation scripts.

It's early days, but I'd love feedback and suggestions about what you'd like to see from a project like this.

GitHub: https://github.com/lacquerai/lacquer | Website: https://lacquer.ai | Docs: https://lacquer.ai/docs

Thanks for checking it out!

https://redd.it/1mslngo
@r_devops

UPDATE: 24 hours later - built the terminal assistant you told me to build

Hey r/devops!

Yesterday I asked about building a local terminal tool for plain English commands. You gave me brutal (helpful) feedback. Today I have a working demo.

# What you demanded, what I built:

"Don't auto-execute, show me the command first" → Done
"Explain what each part does so people learn" → Added --learn mode
"Make it actually local, not another ChatGPT wrapper" → Curated command database
"Prove it works with a real example" → Live demo at praxis.hezico.com

# Here's what 24 hours of coding looks like:

Built a visual terminal demo showing exactly how this would work - you're troubleshooting a container that keeps crashing at 3AM.

The animated walkthrough shows:

Plain English: "which container keeps restarting and why"
Tool analyzes and suggests kubectl diagnostic commands
Safety prompt: "Execute this safe, read-only diagnostic plan? \[y/N\]"
Shows realistic output finding the OOMKilled container
Demonstrates the --learn command that explains syntax
Shows the business value (faster resolution, air-gap friendly, etc.)

# The visual demo: praxis.hezico.com

60-second terminal animation showing the complete incident workflow and how the confirmation/explanation system works.

# What I learned from your feedback:

1. Security concerns are real \- so everything is read-only diagnostics first
2. Learning curve matters \- so there's explicit explanation mode
3. Trust is earned \- so I show exactly what commands run and why
4. Context matters \- so it suggests logical diagnostic approaches

# Current status:

✅ Working visual demo showing the interaction model
✅ Waitlist to gauge interest and validate demand
🔄 Building the actual CLI tool based on this design
🔄 Adding more command patterns (Docker, systemd, networking, etc.)

# Still want your input:

1. Watch the demo \- does this interaction model make sense?
2. What command scenarios should I prioritize? (Docker debugging? Log analysis?)
3. Would your security team approve this approach vs external AI tools?

If this resonates: praxis.hezico.com \- join the waitlist to stay updated on development

Thanks for the reality check yesterday. This concept is way better because you told me what was broken.

24 hours from idea to concept demo. Worth building the real thing?\# UPDATE: Built the terminal assistant based on your feedback - here's what changed

Hey r/devops and r/sysadmin!

A few days ago I asked about building a local terminal tool that converts plain English to commands. Got tons of feedback (some brutal, all helpful) and spent the weekend building based on your suggestions.

# What you told me to fix:

"Don't auto-execute commands, that's dangerous" ✅ Fixed
"Show the command and explain what it does" ✅ Fixed
"This will make juniors dumber" ✅ Added --learn mode
"What if something breaks and they don't understand it?" ✅ Read-only commands first
"It's just a ChatGPT wrapper" ✅ It's a curated local database, no LLM calls

# Here's what it actually looks like now:

$ ask "which container keeps restarting and why"

🔍 Searching local command database...

📋 Suggested Command:
kubectl get pods --all-namespaces | grep -v Running && kubectl get events --sort-by=.metadata.creationTimestamp

📚 Explanation:
• kubectl get pods --all-namespaces - List all pods across namespaces
• grep -v Running - Filter out healthy running pods
• kubectl get events - Show recent cluster events
• --sort-by=.metadata.creationTimestamp - Sort events chronologically

⚠️ This is a READ-ONLY diagnostic command. Continue? y/N


> y

🚀 Executing...

nginx-prod 0/1 CrashLoopBackOff 47 3h
redis-cache 0/1 ImagePullBackOff 12 1h

Recent Events:
47m Warning BackOff

UPDATE: 24 hours later - built the terminal assistant you told me to build

Hey r/devops!

Yesterday I asked about building a local terminal tool for plain English commands. You gave me brutal (helpful) feedback. Today I have a working demo.

# What you demanded, what I built:

**"Don't auto-execute, show me the command first"** → Done
**"Explain what each part does so people learn"** → Added --learn mode
**"Make it actually local, not another ChatGPT wrapper"** → Curated command database
**"Prove it works with a real example"** → Live demo at [praxis.hezico.com](https://praxis.hezico.com)

# Here's what 24 hours of coding looks like:

Built a visual terminal demo showing exactly how this would work - you're troubleshooting a container that keeps crashing at 3AM.

The animated walkthrough shows:

* Plain English: "which container keeps restarting and why"
* Tool analyzes and suggests kubectl diagnostic commands
* Safety prompt: "Execute this safe, read-only diagnostic plan? \[y/N\]"
* Shows realistic output finding the OOMKilled container
* Demonstrates the --learn command that explains syntax
* Shows the business value (faster resolution, air-gap friendly, etc.)

# The visual demo: [praxis.hezico.com](https://praxis.hezico.com/)

60-second terminal animation showing the complete incident workflow and how the confirmation/explanation system works.

# What I learned from your feedback:

1. **Security concerns are real** \- so everything is read-only diagnostics first
2. **Learning curve matters** \- so there's explicit explanation mode
3. **Trust is earned** \- so I show exactly what commands run and why
4. **Context matters** \- so it suggests logical diagnostic approaches

# Current status:

* ✅ Working visual demo showing the interaction model
* ✅ Waitlist to gauge interest and validate demand
* 🔄 Building the actual CLI tool based on this design
* 🔄 Adding more command patterns (Docker, systemd, networking, etc.)

# Still want your input:

1. **Watch the demo** \- does this interaction model make sense?
2. **What command scenarios** should I prioritize? (Docker debugging? Log analysis?)
3. **Would your security team** approve this approach vs external AI tools?

**If this resonates**: [praxis.hezico.com](https://praxis.hezico.com/) \- join the waitlist to stay updated on development

Thanks for the reality check yesterday. This concept is way better because you told me what was broken.

*24 hours from idea to concept demo. Worth building the real thing?*\# UPDATE: Built the terminal assistant based on your feedback - here's what changed

Hey r/devops and r/sysadmin!

A few days ago I asked about building a local terminal tool that converts plain English to commands. Got tons of feedback (some brutal, all helpful) and spent the weekend building based on your suggestions.

# What you told me to fix:

**"Don't auto-execute commands, that's dangerous"** ✅ Fixed
**"Show the command and explain what it does"** ✅ Fixed
**"This will make juniors dumber"** ✅ Added --learn mode
**"What if something breaks and they don't understand it?"** ✅ Read-only commands first
**"It's just a ChatGPT wrapper"** ✅ It's a curated local database, no LLM calls

# Here's what it actually looks like now:

$ ask "which container keeps restarting and why"

🔍 Searching local command database...

📋 Suggested Command:
kubectl get pods --all-namespaces | grep -v Running && kubectl get events --sort-by=.metadata.creationTimestamp

📚 Explanation:
• kubectl get pods --all-namespaces - List all pods across namespaces
• grep -v Running - Filter out healthy running pods
• kubectl get events - Show recent cluster events
• --sort-by=.metadata.creationTimestamp - Sort events chronologically

⚠️ This is a READ-ONLY diagnostic command. Continue? [y/N]


> y

🚀 Executing...

nginx-prod 0/1 CrashLoopBackOff 47 3h
redis-cache 0/1 ImagePullBackOff 12 1h

Recent Events:
47m Warning BackOff

pod/nginx-prod Back-off restarting failed container
46m Warning Failed pod/nginx-prod Error: OOMKilled

✅ Found your problem: nginx-prod is getting killed for using too much memory
💡 Try: kubectl describe pod nginx-prod -n default


# For the "juniors won't learn" concern:

$ ask "show memory usage" --learn

📚 Command Breakdown:
free -h

• free - Display memory usage statistics
• -h - Human readable format (GB/MB instead of bytes)

💡 Related concepts:
• Virtual vs Physical memory
• Buffer/cache vs actually used memory
• When to worry about memory pressure

📖 Want to learn more? Try: man free


# What makes this different from "just use ChatGPT":

* **Actually local** \- works in air-gapped/secure environments where external AI is blocked
* **Curated commands** \- no hallucinations, just vetted syntax patterns
* **Instant response** \- no API calls, sub-second results
* **Context aware** \- understands your environment and suggests appropriate flags
* **Educational** \- designed to teach, not just execute

# I built a quick demo page: [praxis.hezico.com](https://praxis.hezico.com/)

Shows the full flow with a realistic 3AM incident scenario.

# The honest questions I still have:

1. **Would you actually use this?** Or is the learning curve of a new tool not worth it?
2. **Security teams**: Would you approve a local-only tool vs external AI assistants?
3. **For complex environments**: How important is customization vs out-of-the-box commands?
4. **Pricing model**: One-time purchase, subscription, or freemium?

# What I'm building next:

* **Alpha version** with 100+ common DevOps command patterns
* **Custom command support** \- add your own organization's specific commands
* **Audit logging** \- everything gets logged for security/compliance
* **Plugin system** \- extend with your own command databases

If you want to try the alpha: [praxis.hezico.com](https://praxis.hezico.com/)

Looking for 50-100 DevOps/SRE folks who deal with this pain daily and want to test it in real environments.

**TL;DR**: Took your feedback seriously. Built confirmation prompts, explanations, educational mode, and local-only processing. Still think it's stupid? Let me know why.

*Thanks to everyone who gave honest feedback on the original post. This is way better because of your input.*

https://redd.it/1mso7mb
@r_devops

Looking for a Study Partner in DevOps & AWS

Hello everyone 👋
I’m a junior backend developer with some hands-on experience in managing servers, which sparked my passion for DevOps.

I’m currently transitioning into the DevOps field and have started studying AWS. Alongside this journey, I’m also looking for an internship or junior-level opportunity where I can gain real-world experience and grow further.

💡 To stay motivated and make the learning process more effective, I’d love to connect with someone who shares the same interest in DevOps / Cloud (AWS) to do pair studying — exchanging knowledge, practicing together, and keeping each other accountable.

If you’re on a similar path or know someone who is, let’s connect! 🤝

https://redd.it/1msrv3o
@r_devops