Reddit DevOps – Telegram
Our enterprise cloud security budget is under scrutiny. We’re paying $250K for current CNAPP, Orca came in 40% cheaper. Would you consider switching?

Our CFO questioned our current CNAPP (wiz) spend at $250K+ annually in the last cost review. Had to find ways to get it down. Got a quote from Orca that's 40% less for similar coverage.

For those who've evaluated both platforms is the price gap justified for enterprise deployments? We're heavy on AWS/Azure with about 2K workloads. The current tool works but the cost scrutiny is real.

Our main concerns are detection quality, false positive rates, and how well each integrates with our existing CI/CD pipeline. Any experiences would help.

https://redd.it/1qkwfrx
@r_devops
Incident management across teams is an absolute disaster

We have a decent setup for tracking our own infrastructure incidents but when something affects multiple teams it becomes total chaos. When a major incident happens we're literally updating three different places and nobody has a single source of truth. Post mortems take forever because we're piecing together timelines from different tools. Our on call rotation also doesn't sync well with who actually needs to respond. I wonder, how are you successfully handling cross functional incident tracking without creating more overhead?

https://redd.it/1qkzwlf
@r_devops
Advice Failed SC

So I wanted to get some advice from anyone who's had this happen or been through anything similar.

For context today I've just failed my required SC which was a conditional part of the job offer.

Without divulging much info it wasn't due to me or anything I did it was just to an association with someone (although haven't spoke to them in years) so I was/am a bit blindsided by this as I'm very likely to be terminated and left without a job.

Nothing has been fully confirmed yet and my current lead/manager has expressed he does not want to lose me and will try his best to keep me but its not fully his decision and termination has not been taken off the table.

Any advice/guidance?

https://redd.it/1ql1oim
@r_devops
Kubernetes IDE options

Hey everyone, I am currently using Lens as k8s IDE but it consumes too much resources it seems. I want to change it. So I wonder what Kubernetes IDE you are using.

https://redd.it/1ql1ncy
@r_devops
I have tons of commit in by hands-on project just to verify CI pipeline. how professional solve this problem ?

I have a pipeline to test my app and if it passes, push the new image of the app to github, but github actions require my secret key for a specific feature. I want to run the app in kubernetes statefulset so I deactivate my secret key require feature. but every change I done in my yaml files or in webapp code, I have to push it to github repo, so it will trigger actions and if it pass the test step, it will move to push new image step and my statefulset can pull the latest image and I can see that change I have done effect my statefulset.
so if I want to add a feature in my webapp, I have to think run it in my local, then I have to think about will it be problem in github actions and statefulset.
I just too tried from this cycle. is there any way to test my github actions before I push it to github repo? or how you guys test your yaml files ?

here is my solutions :
1 - Instead pull the image from the repo, I can create the image locally and I can try, but I won't know will it pass my test step of pipeline
2 - I can create a fork from the main repo and push too many commit, when I merge it with main, it will look 1 commit
3 - I find an app named "act" to run github actions locally, but they are not pulling variables from github repo

https://redd.it/1ql4fq1
@r_devops
How are you actually handling observability in 2026? (Beyond the marketing fluff)

Every year observability gets pitched as simpler and basically solved. Unified platforms, clean dashboards, smarter alerts.

In reality, when something breaks it still feels messy.

I am curious how people are actually handling this in 2026. What does observability look like for you in practice right now.

https://redd.it/1qlj4h7
@r_devops
DevOps Vouchers Extension

Hi

I bought a DevOps foundation and SRE exam voucher from the DevOps institute back in 2022.
A few life events happened and I wasn't able to give the exam. I'd like to attempt the exams now.

The platform was webassessor back then. Now i think its peoplecert.

I emailed their customer support and the people cert team picked up stating they have no records of my purchase.

I can provide the receipt emails, voucher codes and my email id for proof of payments.

Any one who encountered such an issue before or knows how to resolve?

Will really appreciate because its around $400 of hard earned money



https://redd.it/1qllumj
@r_devops
From DevOps Engineer to Consultant

Has anyone in Europe gone from a DevOps engineer role to work self employed in Europe? How easy or difficult is it? Any tips on how to do the change?

https://redd.it/1qlmufo
@r_devops
curl killed their bug bounty because of AI slop. So what’s your org’s “rate limit” for human attention?

curl just shut down their bug bounty program because they were getting buried in low-quality AI “vuln reports.”

This feels like alert fatigue, but for security intake. If it’s basically free to generate noise, the humans become the bottleneck, everyone stops trusting the channel, and the one real report gets lost in the pile.

How are you handling this in your org? Security side or ops side. Any filters/gating that actually work?

Source: https://github.com/curl/curl/pull/20312

https://redd.it/1qlqgnt
@r_devops
Udemy course recommendations for a graduate platform enginner

hi all, I'll be starting my first job as a graduate platform engineer soon

so i would like enquire about what udemy courses would you recommend to get a graduate platform engineer up to speed as fast as possible, as they are to many courses on udemy to choose from.

all recommendations and advice is greatly appreciated, thanks

https://redd.it/1qlug67
@r_devops
A CLI to Tame OWASP Dependency-Track Version Sprawl in CI/CD

Like many of you, I struggled with automating Dependency-Track. Using curl was messy, and my dashboard was flooded with hundreds of "Active" versions from old CI builds, destroying my metrics.

I built a small CLI tool (Go) to solve this. It handles the full lifecycle in one command:

* Uploads the SBOM.
* Tags the new version as Latest.
* Auto-archives old versions (sets active: false) so only the deployed version counts toward risk scores.

It’s open source and works as a single binary. Hope it saves you some bash-noscripting headaches!

Repo: [https://github.com/MedUnes/dtrack-cli](https://github.com/MedUnes/dtrack-cli)

https://redd.it/1qm066u
@r_devops
Is there any useful tool that allows you to test your kubernetes configs without deploying or running it locally?

Is there any useful tool that allows you to test your kubernetes configs without deploying or running it locally? I am wondering if there's anything like that, because I have a large config with a lot of resources.

https://redd.it/1qm89l8
@r_devops
How should i pivot to devops, without losing half my salary?

Hey guys,

Here’s my situation. I’m currently working as a Cloud Engineer, mostly with IaaS, PaaS and IaC. I’ve been in the cloud space for about a year now, and overall I have around 5–6 years of IT experience.

In the cert side, i have AZ-900, AZ-104, AZ-305, and AZ-400

In my current role I worked my way up to a medior level, but my real goal is to move into DevOps. I know that means I need solid Docker and Kubernetes knowledge, so I’ve started learning and practicing them in my limited free time. I’ve even built some small projects already.

The problem is that my current salary is around standard market level, which is great, but when I apply for DevOps roles, I usually run into two outcomes:

1, I don’t even get invited to an interview,

2, I get an interview, but they offer me about half my current salary because they would hire me as a junior DevOps engineer due to my lack of hands-on experience with Docker and Kubernetes.

Right now I simply can’t afford to cut my salary in half. On top of that, my current company doesn’t really use Docker or Kubernetes, so I don’t have the chance to gain real work experience with them.

I know the market is shit for switching jobs right now, but living in a country where salaries are already much lower than in most of Europe makes this even more frustrating. Honestly, it’s hard to see a clear way forward.

What would you do in my situation? How would you successfully pivot into DevOps without taking such a big financial step back? Any advice would be really appreciated.

https://redd.it/1qmcemd
@r_devops
Ingress NGINX retires in March, no more CVE patches, ~50% of K8s clusters still using it

Talked to Kat Cosgrove (K8s Steering Committee) and Tabitha Sable (SIG Security) about this. Looks like a ticking bomb to me, as there won't be any security patches.

TL;DR: Maintainers have been publicly asking for help since 2022. Four years. Nobody showed up. Now they're pulling the plug.

It's not that easy to know if you are running it. There's no drop-in replacement, and a migration can take quite a bit of work.

Here is the interview if you want to learn more https://thelandsca.pe/2026/01/29/half-of-kubernetes-clusters-are-about-to-lose-security-updates/

https://redd.it/1qqkqzn
@r_devops
Observability is great but explaining it to non-engineers is still hard

We’ve put a lot of effort into observability over the years - metrics, logs, traces, dashboards, alerts. From an engineering perspective, we usually have good visibility into what’s happening and why.

Where things still feel fuzzy is translating that information to non-engineers. After an incident, leadership often wants a clear answer to questions like “What happened?”, “How bad was it?”, “Is it fixed?”, and “How do we prevent it?” - and the raw observability data doesn’t always map cleanly to those answers.

I’ve seen teams handle this in very different ways:

curated executive dashboards, incident summaries written manually, SLOs as a shared language, or just engineers explaining things live over zoom.

For those of you who’ve found this gap, what actually worked for you?

Do you design observability with "business communication" in mind, or do you treat that translation as a separate step after the fact?

https://redd.it/1qqfjzu
@r_devops
Yet another Lens / Kubernetes Dashboard alternative

Me and the team at Skyhook got frustrated with the current tools - Lens, openlens/freelens, headlamp, kubernetes dashboard... all of them we found lacking in various ways. So we built yet another and thought we'd share :)

Note: this is not what our company is selling, we just released this as fully free OSS not tied to anything else, nothing commercial.

Tell me what you think, takes less than a minute to install and run:

https://github.com/skyhook-io/radar

https://redd.it/1qqk10r
@r_devops
our ci/cd testing is so slow devs just ignore failures now"

we've got about 800 automated tests running in our ci/cd pipeline and they take forever. 45 minutes on average, sometimes over an hour if things are slow.

worse than the time is the flakiness. maybe 5 to 10 tests fail randomly on each run, always different ones. so now devs just rerun the pipeline and hope it passes the second time. which obviously defeats the purpose.

we're trying to do multiple deploys per day but the qa stage has become the bottleneck. either we wait for tests or we start ignoring failures which feels dangerous.

tried parallelizing more but we hit resource limits. tried being more selective about what runs on each pr but then we miss stuff. feels like we're stuck between slow and unreliable.

anyone solved this? need tests that run fast, don't fail randomly, and actually catch real issues.

https://redd.it/1qr00b5
@r_devops
made one rule for PRs: no diagram means no review. reviews got way faster.

tried a small experiment on our repo. every PR needed a simple flow diagram, nothing fancy, just how things move. surprisingly, code reviews became way easier. fewer back-and-forths, fewer “wait what does this touch?” moments. seeing the flow first changed how everyone read the code.

curious if anyone else here uses diagrams seriously in dev workflows??



https://redd.it/1qr131v
@r_devops
Build once, deploy everywhere and build on merge.

Hey everyone, I'd like to ask you a question.

I'm a developer learning some things in the DevOps field, and at my job I was asked to configure the CI/CD workflow. Since we have internal servers, and the company doesn't want to spend money on anything cloud-based, I looked for as many open-source and free solutions as possible given my limited knowledge.

I configured a basic IaC with bash noscripts to manage ephemeral self-hosted runners from GitHub (I should have used GitHub's Action Runner Controller, but I didn't know about it at the time), the Docker registry to maintain the different repository images, and the workflows in each project.

Currently, the CI/CD workflow is configured like this:

A person opens a PR, Docker builds it, and that build is sent to the registry. When the PR is merged into the base branch, Docker deploys based on that built image.

But if two different PRs originating from the same base occur, if PR A is merged, the deployment happens with the changes from PR A. If PR B is merged later, the deployment happens with the changes from PR B without the changes from PR A, because the build has already happened and was based on the previous base without the changes from PR A.

For the changes from PR A and PR B to appear in a deployment, a new PR C must be opened after the merge of PR A and PR B.

I did it this way because, researching it, I saw the concept of "Build once, deploy everywhere".

However, this flow doesn't seem very productive, so researching again, I saw the idea of ​​"Build on Merge", but wouldn't Build on Merge go against the Build once, deploy everywhere flow?

What flow do you use and what tips would you give me?

https://redd.it/1qqhrbs
@r_devops
ECR alternative

Hey all,

We’ve been using AWS ECR for a while and it was fine, no drama. Now I’m starting work with a customer in a regulated environment and suddenly “just a registry” isn’t enough.

They’re asking how we know an image was built in GitHub Actions, how we prove nobody pushed it manually, where scan results live, and how we show evidence during audits. With ECR I feel like I’m stitching together too many things and still not confident I can answer those questions cleanly.

Did anyone go through this? Did you extend ECR or move to something else? How painful was the migration and what would you do differently if you had to do it again?

https://redd.it/1qr2zq2
@r_devops
What internal tool did you build that’s actually better than the commercial SaaS equivalent?

I feel like the market is flooded with complex platforms, but the best tools I see are usually the noscripts and dashboards engineers hack together to solve a specific headache.
​Who here is building something on the side (or internally) that actually works?

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