r/devops • • May 20 '24

Kubernetes is overrated, change my mind.

1 Upvotes

My experience is with smaller companies so take this with a grain of salt... But at what point does it really become worth it for a company? I'm sure the answer will be "it depends", but I'd love to hear experiences when you saw kubernetes in use where it really was the best tool for the job, and others where it wasn't.


r/devops • • Dec 22 '25

LLMs in prod: are we replacing deterministic automation with trust-based systems?

2 Upvotes

Hi,

Lately I’m seeing teams automate core workflows by wiring business logic in prompts directly to hosted LLMs like Claude or GPT.

Example I’ve seen in practice: a developer says in chat that a container image is ready, the LLM decides it’s safe to deploy, generates a pipeline with parameters, and triggers it. No CI guardrails, no policy checks, just “the model followed the procedure”.

This makes me uneasy for a few reasons:

•	Vendor lock-in at the reasoning/decision layer, not just APIs

•	Leakage of operational knowledge via prompts and context

•	Loss of determinism: no clear audit trail, replayability, or hard safety boundaries

I’m not anti-LLM. I see real value in summarization, explanation, anomaly detection, and operator assistance. But delegating state-changing decisions feels like a different class of risk.

Has anyone else run into this tension?

•	Are you keeping LLMs assistive-only?

•	Do you allow them to mutate state, and if so, how do you enforce guardrails?

•	How are you thinking about this from an architecture / ops perspective?

Curious to hear how others are handling this long-term.


r/devops • • Dec 18 '21

Is Terraform is the only choice in 2021/2?

30 Upvotes

I've been looking at Terraform and know it's very powerful and mainstream.

My only issues:

  • HCL language is an interesting DSL, but would prefer just using a mainstream language, but I know CDKTF exists but this seems very young at the moment?

  • Terraform state, this deeply troubles me, I think HashiCorp has made a major architecture flaw, a permanent state shouldn't be ever needed in theory at least, however having ephemeral state that can be re-generated would be a good optimisation.

What alternatives are there that is:

  • Free open source

  • Doesn't use state

  • Uses mainstream language and no custom DSL

EDIT

For all those downvoting, it's very amusing that you immediately jump to conclusions rather then actually explaining the problem at hand, if you don't actually know then better to just say so.

What no one has actually answered despite all the comments is WHY a disjointed state is required and then endlessly kept in sync (along with locks) with the real resources, when technically simply observing the real resources would actually negate the need to keep said disjointed state in sync in the first place . Only one comment has actually come half way to answering this.

So please instead of a tribalistic downvotes I would rather prefer well reasoned feedback?

And if such a tool doesn't exist, I guess I'll have to build one, I might as well since I'm already building a Kubernetes alternative 🤷‍♂️

EDIT 2

ok so now after reading some of the newer comments, it appears Terraform can import state if needed, however as some have explained the reason why state needs to be "captured" Terraforms side (the disjointed state) is that Terraform has no way of knowing what it has created and what has potentially been created outside of Terraform "out of band" or manually (technically it could use tagging/naming to embed the meta information, however not all resources actually have a tag/name, that's a physical limitation of the cloud provider)

Now this just raises another question:

The only issue of not being able to discern what is created by Terraform Vs what is created outside of it is ONLY an issue if you're not doing IaC in the first place.

Now we have a contradiction, if you say that Terraform is IaC then it doesn't matter as the declaration of resources in Terraform should be all that is, that would be true IaC.

If you say that it needs to consider non IaC defined resources then that by definition isn't IaC, you can't have it both ways!

EDIT 3:

so based on more comments, I've come to the following summary:

none of the existing tools are strictly IaC (but that's more due to a limitation of the existing cloud provider implementation) .

However while it's not technically pure/true IaC (see EDIT 2) if one ignores the disjointed state and pretends it doesn't it exists or is just an implementation detail, you could say it's "good enough IaC".

Anyway with that in mind, it seems at the moment Pulumi ticks both open source as well as using mainstream languages so that will be my focus for now.

Pulumi also uses state like Terraform so it's not perfect either (i.e not a true IaC) but that's the limitation we have to live with I guess?


r/devops • • Sep 15 '24

DevOps Transformation: Why Principles Matter More Than Tools 🚀

6 Upvotes

Hey everyone,

I recently wrote an article on why focusing on principles rather than just tools is crucial for a successful DevOps transformation. Would love to get your thoughts on it!

👉 Check it out here

Thanks for reading!


r/devops • • Jan 16 '25

Docker: still worth relearning?

0 Upvotes

I'm not trying to make myself super marketable, but I also don't want to learn a dying technology. I used to know basic docker skills about 10ish years ago (give or take), and I'm wanting to spin up some basic web apps partly for the fun of it. Is docker worth investing my time or should I leverage something else to handle my infra needs?

EDIT: Mentioned in a comment below, but since there's a few saying this, just wanted to clear up... I don't think that docker is dying - I just have been away from it for so long that I want sure on the lifecycle of tech where it was at. Generally speaking, I don't want to learn/use any technology that's known to be on the decline.


r/devops • • Mar 18 '19

Why most companies don't need Kubernetes

0 Upvotes

We recently wrote a blog post about why most companies don't need Kubernetes. You can read about it here:

https://scalarsoftware.com/blog/why-most-companies-dont-need-kubernetes/


r/devops • • Aug 02 '25

Cert expired (again). Built a tool to stop the madness, Curious what DevOps folks think

0 Upvotes

You know that moment when everything breaks on a Sunday morning because someone forgot to renew a TLS cert?

Yeah. Me too. Too many times.

So I built a tool, (I don't want to post the link here, because I don't want to spam, I'm looking for feedback) a certificate monitoring and management tool built for real-world DevOps setups.

It handles:

  • Public domains, keystores, cert folders

  • Internal mTLS certs, air-gapped systems, embedded devices

  • Azure Key Vault, HashiCorp Vault, and more coming soon

  • Offline-friendly agent (keymon — npm link)

  • Expiry alerts, tagging, environment grouping, ownership context

Basically: stop the tribal knowledge, spreadsheets, and “who owns this cert?” fire drills.

Curious how the DevOps crowd is managing internal certs these days, scripts? Prometheus exporters? Or just hoping Let’s Encrypt doesn’t let you down?

Would love feedback if you want to give it a spin, let me know and we can chat "offline", or just roast it if you hate certs as much as I do 😂


r/devops • • Dec 12 '21

Why Linux is needed for DevOps in 2021?

0 Upvotes

This question come of course from a total noob. Please, do not be harsh on me. I just could not find detailed answer and some people that I know, don't use linux at all and while they are not 100% time DevOps, they never needed a linux on their PC. Maybe this is true only if you are doing only some basic stuff and you are not full DevOps guy?

As far as I know, most stuff just works on Windows right now (docker, kubernetes, ansible etc). Do they works much better on Linux tho? Is there anything that just does not work on Windows and just require Linux?

I know that most of the cloud run on Linux but if you are working with AWS or Azure, you still work with everything by using either AWS or Azure portal or this looks different and for example you need to use console a lot and thus ssh to the server etc?


r/devops • • Jul 21 '24

Anyone hire someone right out of school for DevOps?

0 Upvotes

If so, how did it go? My team is considering hiring for an associate/fresh grad.


r/devops • • Jan 26 '26

AI content I built two MCP tools for my team and they’re changing how we investigate issues

0 Upvotes

I’ve been experimenting with MCP tools at work and ended up building two that have actually stuck:

  1. RAG / knowledge search tool

Our knowledge is scattered across wikis, docs, code, and tickets. The RAG tool queries all of it and returns URLs, so it ends up being a better search than anything we had before. My team rarely looks things up manually anymore. We just ask and verify straight at the source.

2) Log retrieval tool

This one’s been a big time saver. Instead of auth’ing into service accounts to pull logs, the tool runs a CloudWatch query and writes results to local JSON files that the agent can read.

These tools work hand-in-hand. We can get AI to analyze the log outputs and then use the knowledge base to reason about what’s going on. Logs + context together has been far more useful than either on its own.

The learning feedback loop

What really made this work for us was creating context docs for common issues: what log groups to look into, what queries to run, and what to look for.

After every investigation we ask: what information would the agent have needed to do this automatically next time? The best way we’ve found to do this is to just ask the agent:

“From what you learned during this investigation, how would you update the investigation context document?”

The agent is already capable of handling common investigations that each used to take us 10+ minutes of manual digging.

How it’s built (high level)

•	Lambda parses docs, wikis, code, and tickets and writes them to S3

•	Bedrock knowledge bases with OpenSearch Serverless for embeddings from data in S3

•	We use Kiro as the assistant orchestrating the MCP tools

MCP tools are intentionally simple:

•	The RAG tool just queries the knowledge base and returns the response plus citation URLs

•	The log tool runs a CloudWatch query and writes results to local files instead of dumping logs directly into context

One thing I learned quickly is you don’t want MCP tools doing too much. Let the agent do the reasoning. Tools should just fetch.

What MCP tools have you built that you actually find useful day-to-day? I’m looking for ideas on what to build next.


r/devops • • Oct 10 '26

Tools Ipv4 vs Ipv6, explained from scratch

Thumbnail
youtu.be
0 Upvotes

r/devops • • Jul 26 '25

API GATEWAY

4 Upvotes

I have been tasked to create a prototype for an API gateway for my company which we shall sell as a saas. I have not done such a project before and here is how i have been thinking about approaching the problem.

  1. Use Nginx as a reverse proxy then business logic in Go or C/C++ and Redis pub/sub for caching.

  2. Coming up with a reverse proxy first then modifying it into a gateway

  3. Just start everything from scratch.

am a junior and i have never encountered such, if there is a better way and please guide . help align my thinking


r/devops • • May 29 '24

Kubernetes is not DevOps.

0 Upvotes

See it time and time again here with people asking what to learn or creating roadmaps for DevOps saying you "need" Kubernetes (K8S) but that's such an incorrect statement.

Are there companies out there that use it and want you to have it? Sure. Many of those will never actually leverage it in the way it is constructed. Often times you will spend more time fixing issues with Kubernetes than you would other solutions. Kubernetes is container orchestration at scale, At Scale means "large volumes", which many companies don't have. I have worked for larger companies whose clusters almost never scaled and when they did they were minor. To the point that they spent more on K8S management, upkeep, and spending (servers on prem or cloud cost) than they made with systems on K8S.

Does this mean those companies built it incorrectly? Not all the time, no, it more often mean s that they were sold a solution for a problem they didn't have.

I want to be clear, you should ensure you learn Containerization. That is a modern framework for handling any application that's been made for or updated to handle it. Containers can be deployed on a variety of systems, both Kubernetes and not, and should be leveraged as such.

This ultimately comes down to a business case. Are you scaling, or planning to scale, at high levels? Say over 100 or 500 or greater? Yep Kubernetes is probably the solution you want at that point. Are you scaling less than 100, or 50, or 10? Other solutions are capable to assist you here for less cost and work.

From the azure end alone you have Container Instances and App Services which can host containers natively for both Windows and Linux. They have scale settings to allow up or out. They also have a much lower management overhead and cost overhead associated to them. AWS and GCP both have similar offerings that can be used instead.

Should you learn Version Control (git in most cases), a programming language (optional usually depending on the role you want), monitoring, log handling, IaC, Containerization, scripting, CI/CD? Yes to almost all. Should you learn Kubernetes? Only if the jobs you want need it.


r/devops • • Mar 28 '24

How do I avoid having to do DevOps and seeing people complain about asking how to do it? Can we ban DevOps Post?

3 Upvotes

I’m a software engineer and I don’t like doing DevOps even though I do it being I work at a small company. I mean every question has already been asked and answered with a basic search of this sub. If you can’t search this sub then you probably should look into doing something that you like and make it some other unfortunate non DevOps person problem to complain on the sub.

Clearly this is satire: I see people complaining about it all the time and I’m not even in this sub.


r/devops • • Feb 09 '26

Ops / Incidents Is GitHub actually down right now? Can’t access anything

0 Upvotes

GitHub seems to be down for me pages aren’t loading and API calls are failing.
Anyone else seeing this? What’s the status on your side?


r/devops • • Mar 12 '24

Upskilling: What is a niche skill in DevOps?

0 Upvotes

I’m looking for upskilling myself. I am a 5 year experienced DevOps engineer(In India) looking to upskill myself for US job market since I’ll be immigrating shortly.

Looking for a niche skill to learn to have an edge with my competitors. Any ideas?


r/devops • • Mar 11 '24

Why do so many people say "Fargate" when they refer to deploying their app? It is ECS or EKS, but not Fargate. Am I wrong?

0 Upvotes

Hello. I completely forgot about this one but this morning one of my colleagues once again said "We can look at deploying our app in Fargate".

And at some time in past I read so many blogs mentioning the same thing, something like "How to run your application on Fargate". Where did it start?

So from what I know, Fargate is just a new type of compute in AWS, abstracting away the management of EC2 from you, of course at a cost and with some limitations. You would still be using either ECS or EKS. And the two are not the same.

Or am I the uggly duckling who does not understand and agree with labeling everything "yay let's go fargate hell yeah".

Update: To those who sacrasticaly replied, well I am sorry that I missed the memo about "Fargate used to be ECS only." At least 3 years ago when I started with AWS it was already available for EKS so I did not know until you clarified. And I know what Fargate is and how it works.

Perhaps you also needed context. Not all organisations that talk about AWS and or Fargate, are already cloud native and etc. My company only starting to scratch the surface of possibility to moving to containers, up till now we are still running a monolith on virtual machines. So in this context, saying "let's look at Fargate" can be really cryptic.

Thank you for your replies and downvotes. Now this explains with a bit of the history.


r/devops • • Feb 23 '26

Ops / Incidents A "harmless" field rename in a PR broke two services and nobody noticed for a week

0 Upvotes

Had a PR slip through last month where someone renamed a response field as part of a cleanup. looked totally harmless in the diff. broke two downstream services, nobody caught it for a week until someone pinged us asking why their integration was failing silently.

we ended up adding openapi spec diffing to CI after that so structural breaks get flagged before merge. been working well but it only catches the obvious stuff like removed fields or type changes, not behavioral things like default values shifting.

curious what other teams do here. just code review and hope for the best? contract tests? something else?


r/devops • • Sep 08 '25

What’s the most underrated tool or practice in your DevOps workflow?

7 Upvotes

I feel like DevOps conversations often revolve around the big names (Docker, Kubernetes, Terraform, Jenkins, etc.), but there are tons of smaller tools, scripts, or practices that silently save us hours every week.

Curious! what’s that one underrated tool, plugin, or workflow hack that you swear by but rarely see mentioned in discussions?


r/devops • • Jul 24 '21

I hate the cloud

0 Upvotes

Over last few years I designed or redesigned multiple different infrastructures (all as IaC, some with k8s stuff) and worked on few more. All of those were on prem stuff built on top of open source tools (with some proprietary bullshit I had no influence over, VMware, Oracle etc).

My growth as an engineer was mostly iterative, I was building skills on top of previous experience with similar standards and tools. It was all I wanted from my job, cause it was in sync with my views on software (foss first, proprietary vendor lock only if there is no choice).

Recently when I was looking for new client to work for (I run a single person business, it has some financial and freedom related benefits in my country), I've noticed that 90% of the job offers involve some kind of cloud environment, so I figure, it's time to get better idea about it.

I never held cloud in high regard, cause it seemed like a worst possible vendor lock in, just better marketed. Sadly it had to be done.

Few months into the project as a more of a cloud architect (though I write automation too), I find myself learning stuff that does not translate into anything else, but single vendor product. Unlike my previous experiences, none of this is going to benefit me if I have to change project into something that uses different cloud provider or even on-prem stuff.

I suspect without some legislation about standards in the cloud (like not allowing cloud providers to create proprietary APIs or vendor specific tools), this is only going to get worse.


r/devops • • May 14 '17

Immutable infrastructure can be dramatically more secure

0 Upvotes

We switched to immutable servers and found it much easier to secure our sites. Detecting changes when you are doing updates, patches and upgrades becomes quite difficult. Immutable servers don't have this issue and thus it is much easier to detect a whole class of hacks.

Here is a full post about it: https://simplesecurity.sensedeep.com/immutable-infrastructure-can-be-dramatically-more-secure-238f297eca49


r/devops • • Apr 27 '25

Does anyone here actually do Devops? (_real_ Devops)

0 Upvotes

My last job was in a devops org, let me describe it.

We had a "pizza" sized team (5-8 people) with a range of skills. A who was good with AWS, T who was good at testing, C who was good at code, S who was good at scrum (and a few less experienced juniors).

But, if S was out, then C could run the standup. C actually understood the unit test framework we inherited better than T. Most of the work was coding so T, S and A spent most of their time writing code. And the juniors could chair a meeting, write code, tests or deploy to AWS (with supervision/code review). If there was a bug report, anyone would pick it up and if they needed, would ask someone. PR reviews would always include a "did you update the docs check?" (iirc the cicd would actually reject PRs that had changes in the API code but no docs change). We were responsible for our own product's security and used various tools to alert us to code/IaaC problems. Each PR would get its own test environment and we'd deploy changes multiple times a day.

And there were about 10 teams all doing the same in our business unit. And if we needed to interface with one of them we'd read their documentation and if they needed us, they'd read ours.

Every time I come to this sub, I seem to be reading a post from someone annoyed with either:

  • "devops" then describes one part of devops like it's all of devops (eg "I hate devops because [test|CICD|security] is hard")

  • "devs" describing them as a separate evil entity

  • "ops" describing them as a separate evil entity

  • "security" describing them as a separate evil entity

If you're in a "devops" team and are not developing, testing, securing, operating, improving your product: you're doing it wrong.

If you're in a "devops tools" team and not doing devops yourself: Why not? And by the way, providing the devops tools should not include providing CICD code for projects or defining monitoring or logging or responding to tickets.

So, do YOU do devops?

(As a consequence, I think "normal" dev with 2 years experience is starting to be not junior. But because devops includes so many disciplines, you can still be a junior devops with 5 years experience. Only with that amount of experience can you be expected to have useful amounts of experience of typescript, python, java, bash and sql and unit tests and investigate IAM, DNS, kernel, firewall and routing issues and respond to customer tickets and configuring Tekton/ArgoCD/Jenkins)


r/devops • • Nov 22 '23

What can DevOps Engineers actually do? Fix all your problems and do your taxes for you?

0 Upvotes

As DevOps engineers, we are often asked to go outside of our remit and fix all the world's problems. This always drives me insane! We can't magically make a Legacy app, state-of-the-art and bleeding edge, but as DevOps engineers, we control the architecture! Making changes to the architecture can have massive benefits and drive these applications into the modern age.

Moving applications to run in containers is usually the first leap forward and allows for much more innovation to take place. This is where the fun begins! Once an application is containerised, it allows us to move the container to run in environments like Kubernetes and move to pub-sub architecture by making small changes to the entry points of the containers and now the world is your oyster! Better logging, better monitoring, better error handling, actual CI/CD and more. So many benefits to taking that small leap into containers.

Kubernetes is usually slated as the DevOps engineers silver bullet. The one thing used to fix everything! I usually hate that idea and plead with engineers to not think this way but some times... it really is the fix haha.

Have you ever encountered a development team asking you to fix all their problems without touching the main code??
What are some of your war stories around this?

If you want to read more about our journey, i've written this blog about the evolution of our legacy system.
https://medium.com/@storkey/the-evolution-of-a-legacy-system-95382a79b1dd


r/devops • • Sep 11 '24

What's next for Devops Engineer , is it MLops

0 Upvotes

First we had cloud _

  • then Infra as a Cloud Came (Terraform)

  • Configuration - Ansible -Docker , Kubernetes

  • Helm, Observability

What should be next thing to learn to keep ourselves in the devops market ?

Is it MLops / AIops ?

Anyone working in the ML/AI ops ? How is it ?