🛡️ RELIAKIT TL-15 Open-Source Chaos + Healing Framework for Planet-Grade Infrastructure
Built for resilience engineers, platform teams, and SREs who want more than just monitoring — they want autonomous recovery.
Let me know what you think — would love your input and improvements!
🔗 GitHub again:
https://github.com/zebadiee/reliakit-tl15
🤝 Looking For
• Feedback on architecture
• Contributors to test new zones
• Suggestions for AI drift detection features
• Adoption in real infrastructure setups
https://redd.it/1lk2lli
@r_devops
Built for resilience engineers, platform teams, and SREs who want more than just monitoring — they want autonomous recovery.
Let me know what you think — would love your input and improvements!
🔗 GitHub again:
https://github.com/zebadiee/reliakit-tl15
🤝 Looking For
• Feedback on architecture
• Contributors to test new zones
• Suggestions for AI drift detection features
• Adoption in real infrastructure setups
https://redd.it/1lk2lli
@r_devops
GitHub
GitHub - zebadiee/reliakit-tl15: ReliaKit TL-15 is an open-source, planet-grade resilience framework for distributed infrastructure.…
ReliaKit TL-15 is an open-source, planet-grade resilience framework for distributed infrastructure. It integrates automated DDoS protection, geo-aware routing, chaos engineering, and symbolic AI ho...
Getting a Remote Job is hard – Returning After Maternity Break
I’ve been working in an office-based DevOps role for 10 years. After a brief 2-month maternity leave, I hope to work remotely for at least a year to care for my newborn.
However, reality has hit hard — I’ve been actively applying on LinkedIn and over 20 other platforms for the past two months with zero responses.
I’ve tried all the common remote job sites people recommend, even registered on Toptal, freelancer.com, and many others, but they seem overwhelmed right now.
I’m not outdated — I have solid experience with AWS, GCP, Kubernetes, Linux, Jenkins, Argo, Kafka, and many other widely used tools.
Not sure if I’m doing something wrong or if the market is just this tough. If anyone has any advice, leads, or referrals, I’d deeply appreciate it.
https://redd.it/1lk58xc
@r_devops
I’ve been working in an office-based DevOps role for 10 years. After a brief 2-month maternity leave, I hope to work remotely for at least a year to care for my newborn.
However, reality has hit hard — I’ve been actively applying on LinkedIn and over 20 other platforms for the past two months with zero responses.
I’ve tried all the common remote job sites people recommend, even registered on Toptal, freelancer.com, and many others, but they seem overwhelmed right now.
I’m not outdated — I have solid experience with AWS, GCP, Kubernetes, Linux, Jenkins, Argo, Kafka, and many other widely used tools.
Not sure if I’m doing something wrong or if the market is just this tough. If anyone has any advice, leads, or referrals, I’d deeply appreciate it.
https://redd.it/1lk58xc
@r_devops
Freelancer
Hire Freelancers & Find Freelance Jobs Online
Find & hire top freelancers, web developers & designers inexpensively. World's largest marketplace of 50m. Receive quotes in seconds. Post your job online now.
Any DevOps podcasts / newsletters / LinkedIn people worth following?
Hey everyone!
Trying to find some good stuff to follow in the DevOps world — podcasts, newsletters, LinkedIn accounts, whatever.
Could be deep tech, memes, hot takes, personal stories — as long as it’s actually interesting
If you've got any favorites I'd love to hear about them!
https://redd.it/1lk4l7t
@r_devops
Hey everyone!
Trying to find some good stuff to follow in the DevOps world — podcasts, newsletters, LinkedIn accounts, whatever.
Could be deep tech, memes, hot takes, personal stories — as long as it’s actually interesting
If you've got any favorites I'd love to hear about them!
https://redd.it/1lk4l7t
@r_devops
Reddit
From the devops community on Reddit
Explore this post and more from the devops community
Containerized PDF-OCR Workflow: Trying newly OCRFlux
Hey all, just wanted to share some notes after playing around with a containerized OCR workflow for parsing a batch of PDF documents - mix of scanned contracts, old academic papers, and some table-heavy reports. The goal was to automate converting these into plain Markdown or JSON, and make the output actually usable downstream.
Stack:
- Docker Compose setup with a few containers:
1. Self-hosted Tesseract (via tesseract-ocr/tesseract image)
2. A quick Nanonets test via API calls (not self-hosted, obviously, but just part of the pipeline)
3. Recently tried out OCRFlux - open source and runs on a 3B VLM, surprisingly lightweight to run locally
What I found:
- Tesseract
1. It's solid for raw text extraction from image-based PDFs.
2. Struggles badly with layout, especially multi-column text and anything involving tables.
3. Headers/footers bleed into the content frequently.
4. Works fine in Docker, barely uses any resources, but you'll need to write a ton of post-processing logic if you're doing anything beyond plain text.
- Nanonets (API)
1. Surprisingly good at detecting structure, but I found the formatting hit-or-miss when working with technical docs or documents with embedded figures.
2. Also not great at merging content across pages (e.g., tables or paragraph splits).
3. API is easy to use, but there’s always the concern around rate limits or vendor lock-in.
4. Not ideal if you want full control over the pipeline.
- OCRFlux
1. Was skeptical at first because it runs a VLM, but honestly it handled most of the pain points from the above two.
2. Deployed it locally on a 3090 box. Memory usage was high-ish (\~12-14GB VRAM during heavy parsing), but manageable.
3. What stood out:
- Much better page-reading order, even with weird layouts (e.g., 3-column, Chinese and English mixed PDFs). If the article has different levels of headings, the font size will be preserved.
- It merges tables and paragraphs across pages, which neither Tesseract nor Nanonets handled properly.
- Exports to Markdown that’s clean enough to feed into a downstream search/indexing pipeline without heavy postprocessing.
- Trade-offs / Notes:
1. Latency: Tesseract is fastest (obviously), OCRFlux was slower but tolerable (~5-6s per page). Nanonets vary depending on the queue/API delay.
2. Storage: OCRFlux’s container image is huge. Not a problem for my use, but could be for others.
3. Postprocessing effort: If you care about document structure, OCRFlux reduced the need for cleanup scripts by a lot.
4. GPU dependency: OCRFlux needs one. Tesseract doesn’t. That might rule it out for some people.
TL;DR: If you’re just OCRing receipts or invoices and want speed, Tesseract in a container is fine. If you want smarter structure handling (esp. for academic or legal documents), OCRFlux was way more capable than I expected. Still experimenting, but this might end up replacing a few things in my pipeline.
https://redd.it/1lk6qsx
@r_devops
Hey all, just wanted to share some notes after playing around with a containerized OCR workflow for parsing a batch of PDF documents - mix of scanned contracts, old academic papers, and some table-heavy reports. The goal was to automate converting these into plain Markdown or JSON, and make the output actually usable downstream.
Stack:
- Docker Compose setup with a few containers:
1. Self-hosted Tesseract (via tesseract-ocr/tesseract image)
2. A quick Nanonets test via API calls (not self-hosted, obviously, but just part of the pipeline)
3. Recently tried out OCRFlux - open source and runs on a 3B VLM, surprisingly lightweight to run locally
What I found:
- Tesseract
1. It's solid for raw text extraction from image-based PDFs.
2. Struggles badly with layout, especially multi-column text and anything involving tables.
3. Headers/footers bleed into the content frequently.
4. Works fine in Docker, barely uses any resources, but you'll need to write a ton of post-processing logic if you're doing anything beyond plain text.
- Nanonets (API)
1. Surprisingly good at detecting structure, but I found the formatting hit-or-miss when working with technical docs or documents with embedded figures.
2. Also not great at merging content across pages (e.g., tables or paragraph splits).
3. API is easy to use, but there’s always the concern around rate limits or vendor lock-in.
4. Not ideal if you want full control over the pipeline.
- OCRFlux
1. Was skeptical at first because it runs a VLM, but honestly it handled most of the pain points from the above two.
2. Deployed it locally on a 3090 box. Memory usage was high-ish (\~12-14GB VRAM during heavy parsing), but manageable.
3. What stood out:
- Much better page-reading order, even with weird layouts (e.g., 3-column, Chinese and English mixed PDFs). If the article has different levels of headings, the font size will be preserved.
- It merges tables and paragraphs across pages, which neither Tesseract nor Nanonets handled properly.
- Exports to Markdown that’s clean enough to feed into a downstream search/indexing pipeline without heavy postprocessing.
- Trade-offs / Notes:
1. Latency: Tesseract is fastest (obviously), OCRFlux was slower but tolerable (~5-6s per page). Nanonets vary depending on the queue/API delay.
2. Storage: OCRFlux’s container image is huge. Not a problem for my use, but could be for others.
3. Postprocessing effort: If you care about document structure, OCRFlux reduced the need for cleanup scripts by a lot.
4. GPU dependency: OCRFlux needs one. Tesseract doesn’t. That might rule it out for some people.
TL;DR: If you’re just OCRing receipts or invoices and want speed, Tesseract in a container is fine. If you want smarter structure handling (esp. for academic or legal documents), OCRFlux was way more capable than I expected. Still experimenting, but this might end up replacing a few things in my pipeline.
https://redd.it/1lk6qsx
@r_devops
Reddit
From the devops community on Reddit
Explore this post and more from the devops community
Quick wins to cut your CI/CD costs in half
We've worked with countless teams on optimizing their CI/CD costs. Here are the biggest wins that work regardless of your setup:
Immediate fixes:
Switch to spot instances (60-90% cheaper, works fine for most builds)
Audit your runner idle time - most teams have runners sitting unused 70% of the time
Cache everything aggressively (npm, pip, docker layers, etc.)
Right-size your runners - most builds don't need 8-core machines
Slightly harder but bigger impact:
Parallelize tests intelligently
Kill zombie jobs (set proper timeouts)
Use build matrices only when necessary
Optimize Docker layer ordering
The spot instances thing alone cut one team's AWS bill by 65%. Most CI workloads handle interruptions just fine.
We wrote up a more complete guide if your interested: https://depot.dev/blog/how-to-reduce-cicd-costs-complete-optimization-guide
What's worked for you? Always looking for more optimization tricks.
https://redd.it/1lka3p0
@r_devops
We've worked with countless teams on optimizing their CI/CD costs. Here are the biggest wins that work regardless of your setup:
Immediate fixes:
Switch to spot instances (60-90% cheaper, works fine for most builds)
Audit your runner idle time - most teams have runners sitting unused 70% of the time
Cache everything aggressively (npm, pip, docker layers, etc.)
Right-size your runners - most builds don't need 8-core machines
Slightly harder but bigger impact:
Parallelize tests intelligently
Kill zombie jobs (set proper timeouts)
Use build matrices only when necessary
Optimize Docker layer ordering
The spot instances thing alone cut one team's AWS bill by 65%. Most CI workloads handle interruptions just fine.
We wrote up a more complete guide if your interested: https://depot.dev/blog/how-to-reduce-cicd-costs-complete-optimization-guide
What's worked for you? Always looking for more optimization tricks.
https://redd.it/1lka3p0
@r_devops
Depot
How to reduce CI/CD costs: Complete optimization checklist
Most engineering teams overspend on CI/CD by 50% or more. Here's how to cut your build costs in half without slowing down deployments.
Apple Container: native support for containers on Mac is game changing, or 'meh'?
Apple recently released native support for containers. I've been trying it for local dev stuff like Postgres and Redis, and it is looking fast and lightweight.
Apple came late with this announcement, but I think it might be a big deal. Making the most out of Macs can be soon a reality for containerized apps in production. I have seen big vendors like Github using Mac Minis to run systems in production such as their CI/CD pipelines with Github Actions, maybe this will happen more now that containers are natively supported?
It still lacks support for many things we have in the Docker ecosystem (compose, orchestration tools, etc), but I hope they catch up with the latest docker compatible stuff soon.
What are your thoughts on it? Are you using it or planning to?
I built a terminal UI to make it easy to manage Apple containers. It is written in Go.
https://github.com/andreybleme/lazycontainer
https://redd.it/1lk5wmp
@r_devops
Apple recently released native support for containers. I've been trying it for local dev stuff like Postgres and Redis, and it is looking fast and lightweight.
Apple came late with this announcement, but I think it might be a big deal. Making the most out of Macs can be soon a reality for containerized apps in production. I have seen big vendors like Github using Mac Minis to run systems in production such as their CI/CD pipelines with Github Actions, maybe this will happen more now that containers are natively supported?
It still lacks support for many things we have in the Docker ecosystem (compose, orchestration tools, etc), but I hope they catch up with the latest docker compatible stuff soon.
What are your thoughts on it? Are you using it or planning to?
I built a terminal UI to make it easy to manage Apple containers. It is written in Go.
https://github.com/andreybleme/lazycontainer
https://redd.it/1lk5wmp
@r_devops
GitHub
GitHub - apple/container: A tool for creating and running Linux containers using lightweight virtual machines on a Mac. It is written…
A tool for creating and running Linux containers using lightweight virtual machines on a Mac. It is written in Swift, and optimized for Apple silicon. - apple/container
OpsGenie shutting down, Pagerduty or Rootly?
I sure as hell will not switch my entire workflow / ticketing system over to Atlassian LOL. but i get it, most companies they're targeting probably already have Atlassian contracts.
Stuff I need:
\- integrations with ASPM / DSPM (crowdstrike/groundcover).. i'm not writing lambda functions to convert one alert into another.
\- not charged arm and leg for phone calls
\- slack integration would be a massive plus.
\- good team modelling.
\- different on-call schedules and overrides. if can integrate with HR management system that'd save me so much time LOL
\- don't really care about the UI much, hopefully don't have to log-in more than a few times a month
pricing obviously cheaper better.
looks like both has "easy" migration, where they'll do it for us
thoughts?
https://redd.it/1lkcjxg
@r_devops
I sure as hell will not switch my entire workflow / ticketing system over to Atlassian LOL. but i get it, most companies they're targeting probably already have Atlassian contracts.
Stuff I need:
\- integrations with ASPM / DSPM (crowdstrike/groundcover).. i'm not writing lambda functions to convert one alert into another.
\- not charged arm and leg for phone calls
\- slack integration would be a massive plus.
\- good team modelling.
\- different on-call schedules and overrides. if can integrate with HR management system that'd save me so much time LOL
\- don't really care about the UI much, hopefully don't have to log-in more than a few times a month
pricing obviously cheaper better.
looks like both has "easy" migration, where they'll do it for us
thoughts?
https://redd.it/1lkcjxg
@r_devops
Reddit
From the devops community on Reddit
Explore this post and more from the devops community
Azure - VMSS undergoing maintenance.
Anyone else seeing this over and over today? Im in CentralUS and all my VMSSs are going into maintenance on and off for the last few hours.
https://redd.it/1lkc9m1
@r_devops
Anyone else seeing this over and over today? Im in CentralUS and all my VMSSs are going into maintenance on and off for the last few hours.
https://redd.it/1lkc9m1
@r_devops
Reddit
From the devops community on Reddit
Explore this post and more from the devops community
I have an interview for a Junior DevOps engineer position at EY, what to expect in interview?
So the interview is suppose to be strictly 30 minutes. My guess is it will mostly be behavioral type questions about my background. Does anyone have any experience with this? It's with the IT Risk and Compliance Team.
https://redd.it/1lkfy4z
@r_devops
So the interview is suppose to be strictly 30 minutes. My guess is it will mostly be behavioral type questions about my background. Does anyone have any experience with this? It's with the IT Risk and Compliance Team.
https://redd.it/1lkfy4z
@r_devops
Reddit
From the devops community on Reddit
Explore this post and more from the devops community
what is the best way to learn helm charts?
i have completed a helm charts course on cloud guru and i feel like i get the concept of it well enough but i wouldnt know where to even begin if i were to actually develop a helm chart for an application without using the public repo. which sucks because i have been tasked to do exactly that at work.
to those who are proficient at Helm, what was your learning method? how did you go from watching or reading about it to actually developing working charts?
https://redd.it/1lkh9zi
@r_devops
i have completed a helm charts course on cloud guru and i feel like i get the concept of it well enough but i wouldnt know where to even begin if i were to actually develop a helm chart for an application without using the public repo. which sucks because i have been tasked to do exactly that at work.
to those who are proficient at Helm, what was your learning method? how did you go from watching or reading about it to actually developing working charts?
https://redd.it/1lkh9zi
@r_devops
Reddit
From the devops community on Reddit
Explore this post and more from the devops community
study course or book to learn DevOps from zero to hero
I was googling and there are so many offerings on learning devops i wanted to come on here and ask what is the preferred way to start my journey.
my background is a network engineer, i have used ansible and netmiko python library to run simple repetitive tasks like backing up config on network gear.
thanks
https://redd.it/1lki900
@r_devops
I was googling and there are so many offerings on learning devops i wanted to come on here and ask what is the preferred way to start my journey.
my background is a network engineer, i have used ansible and netmiko python library to run simple repetitive tasks like backing up config on network gear.
thanks
https://redd.it/1lki900
@r_devops
Reddit
From the devops community on Reddit
Explore this post and more from the devops community
Transitioning from Cybersecurity to Cloud Architecture — Advice Welcome
I recently transitioned from a cybersecurity role into a cloud architect position and received a $17K raise—bringing my total comp to $115K. I’ve got around 3 years of experience, hold a master’s degree, and currently work as a Lead Associate with a TS/SCI clearance.
That said… I can’t shake the feeling that I’m still underpaid given my background, skills, and clearance. I'm looking ahead and trying to figure out what’s next in my journey.
Reddit—has anyone made a similar leap or been in this position before? What advice would you give someone trying to level up from here?
https://redd.it/1lkllx0
@r_devops
I recently transitioned from a cybersecurity role into a cloud architect position and received a $17K raise—bringing my total comp to $115K. I’ve got around 3 years of experience, hold a master’s degree, and currently work as a Lead Associate with a TS/SCI clearance.
That said… I can’t shake the feeling that I’m still underpaid given my background, skills, and clearance. I'm looking ahead and trying to figure out what’s next in my journey.
Reddit—has anyone made a similar leap or been in this position before? What advice would you give someone trying to level up from here?
https://redd.it/1lkllx0
@r_devops
Reddit
From the devops community on Reddit
Explore this post and more from the devops community
Introducing DockedUp: A Live, Interactive Docker Dashboard in Your Terminal 🐳
Hello r/devops!
I’ve been working on DockedUp, a CLI tool that makes monitoring Docker containers easier and more intuitive. If you’re tired of juggling
## What My Project Does
DockedUp is a real-time, interactive dashboard that displays your Docker containers’ status, health, CPU, and memory usage in a clean, color-coded terminal view. It automatically groups containers by docker-compose projects and uses emojis to make status (Up 🟢, Down 🔴) and health (Healthy ✅, Unhealthy ⚠️) instantly clear. Navigate containers with arrow keys and use hotkeys to:
-
-
-
-
## Target Audience
DockedUp is designed for developers and DevOps engineers who work with Docker containers and want a quick, unified view of their environment without leaving the terminal. It’s ideal for those managing docker-compose stacks in development or small-scale production setups. Whether you’re a Python enthusiast, a CLI lover, or a DevOps pro looking to streamline workflows, DockedUp is built to save you time and hassle.
## Comparison
Unlike
## Try It Out
It’s on PyPI and takes one command to install (I recommend
Or:
Then run
## Feedback Wanted!
I’d love to hear your thoughts—any features you’d like to see or issues you run into? Contributions are welcome (it’s MIT-licensed).
What’s your go-to way to monitor Docker containers?
Thanks for checking it out! 🚀
https://redd.it/1lkmf9d
@r_devops
Hello r/devops!
I’ve been working on DockedUp, a CLI tool that makes monitoring Docker containers easier and more intuitive. If you’re tired of juggling
docker ps, docker stats, and switching terminals to check logs or restart containers, this might be for you!## What My Project Does
DockedUp is a real-time, interactive dashboard that displays your Docker containers’ status, health, CPU, and memory usage in a clean, color-coded terminal view. It automatically groups containers by docker-compose projects and uses emojis to make status (Up 🟢, Down 🔴) and health (Healthy ✅, Unhealthy ⚠️) instantly clear. Navigate containers with arrow keys and use hotkeys to:
-
l: View live logs-
r: Restart a container-
x: Stop a container-
s: Open a shell inside a container## Target Audience
DockedUp is designed for developers and DevOps engineers who work with Docker containers and want a quick, unified view of their environment without leaving the terminal. It’s ideal for those managing docker-compose stacks in development or small-scale production setups. Whether you’re a Python enthusiast, a CLI lover, or a DevOps pro looking to streamline workflows, DockedUp is built to save you time and hassle.
## Comparison
Unlike
docker ps and docker stats, which require multiple commands and terminal switching, DockedUp offers a single, live-updating dashboard with interactive controls. Compared to tools like Portainer (web-based) or lazydocker (another CLI), DockedUp is lightweight, focuses on docker-compose project grouping, and integrates emoji-based visual cues for quick status checks. It’s Python-based, easy to install via PyPI, and doesn’t need a web server, making it a great fit for terminal-centric workflows.## Try It Out
It’s on PyPI and takes one command to install (I recommend
pipx for CLI tools):pipx install dockedup
Or:
pip install dockedup
Then run
dockedup to start the monitor. Check out the GitHub repo for more details and setup instructions. If you like the project, I’d really appreciate a ⭐ on GitHub to help spread the word!## Feedback Wanted!
I’d love to hear your thoughts—any features you’d like to see or issues you run into? Contributions are welcome (it’s MIT-licensed).
What’s your go-to way to monitor Docker containers?
Thanks for checking it out! 🚀
https://redd.it/1lkmf9d
@r_devops
GitHub
GitHub - anilrajrimal1/dockedup: A real-time, interactive CLI dashboard for monitoring Docker containers. View status, health,…
A real-time, interactive CLI dashboard for monitoring Docker containers. View status, health, CPU, and memory usage with a clean, color-coded interface. Supports docker-compose grouping and hotkeys...
SysDE at AWS worth it?
I'm in an interview loop with AWS for the Systems Development Engineer role building a new region.
My current experience is mainly in AWS, K8s, Python & Shell. The learning opportunities in my current role are great, despite the pay being average. My goal is to maximise my earning potential by getting into big tech, while also having access to learning opportunities, especially in dev side of devops.
Despite the pay at AWS being potentially great, the job description of the SysDE role seems very vague. I haven't been told much other than the fact that it involves Linux and some programmimg.
Anyone been a SysDE at AWS? What's the exact tech stack? How much dev work does it really involve? I'm not sure if doing mostly linux administration is worth the great pay package, if that were the case.
https://redd.it/1lknnyf
@r_devops
I'm in an interview loop with AWS for the Systems Development Engineer role building a new region.
My current experience is mainly in AWS, K8s, Python & Shell. The learning opportunities in my current role are great, despite the pay being average. My goal is to maximise my earning potential by getting into big tech, while also having access to learning opportunities, especially in dev side of devops.
Despite the pay at AWS being potentially great, the job description of the SysDE role seems very vague. I haven't been told much other than the fact that it involves Linux and some programmimg.
Anyone been a SysDE at AWS? What's the exact tech stack? How much dev work does it really involve? I'm not sure if doing mostly linux administration is worth the great pay package, if that were the case.
https://redd.it/1lknnyf
@r_devops
Reddit
From the devops community on Reddit
Explore this post and more from the devops community
Do you spend time optimizing jenkins jobs?
Hey guys,
In our company we have a lot of jenkins jobs almost 400. Some are for deployments used by devs, others are our own for some metric and monitoring stuff.
My manager has been for the past 1-2 years has been focusing much on optimizing on creating common jobs for all the stuff to minimize this number of jobs. Even if they are 4-5 jobs of a type he asks us to create a common job to accumulate these 4 so that if change is required in all then we can change in just one place and everything will work fine. Initially I was involved in creating a common pipeline for all deployments, that went well, we did it. But now he is just asking us to "commonize" every repeating pair or part of jenkins jobs that he sees.
Is this relevant for devops? Will that help with anything? Or is he just trying to solve a problem that never existed? Do you take part in these activities? Will they ever help a devops engineer in any way? Will putting these things in your resume or cv, attract recruiters?
https://redd.it/1lku3k7
@r_devops
Hey guys,
In our company we have a lot of jenkins jobs almost 400. Some are for deployments used by devs, others are our own for some metric and monitoring stuff.
My manager has been for the past 1-2 years has been focusing much on optimizing on creating common jobs for all the stuff to minimize this number of jobs. Even if they are 4-5 jobs of a type he asks us to create a common job to accumulate these 4 so that if change is required in all then we can change in just one place and everything will work fine. Initially I was involved in creating a common pipeline for all deployments, that went well, we did it. But now he is just asking us to "commonize" every repeating pair or part of jenkins jobs that he sees.
Is this relevant for devops? Will that help with anything? Or is he just trying to solve a problem that never existed? Do you take part in these activities? Will they ever help a devops engineer in any way? Will putting these things in your resume or cv, attract recruiters?
https://redd.it/1lku3k7
@r_devops
Reddit
From the devops community on Reddit
Explore this post and more from the devops community
Grafana monitoring
Hello Folks,
Those who are using azure and grafana to visualize the data, how are you querying the data?
We are using SQL to fetch the data however the queries are running frequently and increases the sql usage, we want to avoid relying on SQL?
What is you approach?
https://redd.it/1lkvwt4
@r_devops
Hello Folks,
Those who are using azure and grafana to visualize the data, how are you querying the data?
We are using SQL to fetch the data however the queries are running frequently and increases the sql usage, we want to avoid relying on SQL?
What is you approach?
https://redd.it/1lkvwt4
@r_devops
Reddit
From the devops community on Reddit
Explore this post and more from the devops community
UK Thinking of moving from IT Field Engineer to DevOps
Hey folks,
Been in IT for about 12 years now, basically all I’ve ever done on my life. Started out in tech support and eventually moved up to IT Field Engineer. Still doing hands-on work, and while I enjoy it, I’ve been seriously thinking about shifting into DevOps.
Main reason? DevOps salaries here in the UK look a lot healthier than what I’m on right now, even if I had to start over as a Junior (vs experienced tech).
Due to expire later this year, I’ve got my AWS CCP (never managed to use it in any of my jobs though) and I’ve dabbled in Azure (VM's only) in the past through work. I’ve also done some homelab stuff using Oracle Cloud (free tier) nothing massive, but enough to get some knowledge.
I was considering doing a bootcamp to accelerate things, since I tend to pick up new tech pretty fast. But I’m not sure if it’s worth the investment or if I should just go the self-study route and build a portfolio or certs instead.
Also, curious about how DevOps folks are feeling about AI right now. Within my current role, I’m not too worried, I don’t see AI replacing that any time soon. But what’s your take? Is it changing the DevOps space already? I can feel if the company allows you to use it can be a good allied to work, when comes to makes scripts, etc. Boost on productivity.
Would love to hear any advice or experiences from others who made the switch. Cheers!
https://redd.it/1ll0i3s
@r_devops
Hey folks,
Been in IT for about 12 years now, basically all I’ve ever done on my life. Started out in tech support and eventually moved up to IT Field Engineer. Still doing hands-on work, and while I enjoy it, I’ve been seriously thinking about shifting into DevOps.
Main reason? DevOps salaries here in the UK look a lot healthier than what I’m on right now, even if I had to start over as a Junior (vs experienced tech).
Due to expire later this year, I’ve got my AWS CCP (never managed to use it in any of my jobs though) and I’ve dabbled in Azure (VM's only) in the past through work. I’ve also done some homelab stuff using Oracle Cloud (free tier) nothing massive, but enough to get some knowledge.
I was considering doing a bootcamp to accelerate things, since I tend to pick up new tech pretty fast. But I’m not sure if it’s worth the investment or if I should just go the self-study route and build a portfolio or certs instead.
Also, curious about how DevOps folks are feeling about AI right now. Within my current role, I’m not too worried, I don’t see AI replacing that any time soon. But what’s your take? Is it changing the DevOps space already? I can feel if the company allows you to use it can be a good allied to work, when comes to makes scripts, etc. Boost on productivity.
Would love to hear any advice or experiences from others who made the switch. Cheers!
https://redd.it/1ll0i3s
@r_devops
Reddit
From the devops community on Reddit
Explore this post and more from the devops community
Arachni/Codename-SCNR Shutdown
Arachni was a DAST scanner I had used in previous projects, I went looking for it earlier this year to find out it had been converted to a new project, Codename-SCNR owned by ecsypno.
Here is the origin story, taken from the wayback machine since their site is down:
Origin
Today when going to the site I discovered that it no longer exists:
ECSYPNO
And the only thing I could find was a somewhat cryptic post on twitter from the owner, stating "Ecsypno.com is closing shop for the foreseeable future due to sabotage of my personal and professional lives."
Anyone here a customer? I wonder what will happen to the software for people who have already paid. It was definitely a smaller commercial enterprise, so hopefully not too many orgs are impacted, but it is interesting nonetheless.
https://redd.it/1ll49ke
@r_devops
Arachni was a DAST scanner I had used in previous projects, I went looking for it earlier this year to find out it had been converted to a new project, Codename-SCNR owned by ecsypno.
Here is the origin story, taken from the wayback machine since their site is down:
Origin
Today when going to the site I discovered that it no longer exists:
ECSYPNO
And the only thing I could find was a somewhat cryptic post on twitter from the owner, stating "Ecsypno.com is closing shop for the foreseeable future due to sabotage of my personal and professional lives."
Anyone here a customer? I wonder what will happen to the software for people who have already paid. It was definitely a smaller commercial enterprise, so hopefully not too many orgs are impacted, but it is interesting nonetheless.
https://redd.it/1ll49ke
@r_devops
Ecsypno
The Arachni Chronicles
A story of curiosity, experimentation, development, million euro deal, fraudsters, abandonment and revitalization.
From the inception of the F/OSS Arachni WebAppSec scanner to the opening of Ecsypno’s doors with its flagship product Codename SCNR.
From the inception of the F/OSS Arachni WebAppSec scanner to the opening of Ecsypno’s doors with its flagship product Codename SCNR.
I hate existing doc tooling
I don't think this breaks community guidelines (I post here regularly), if I am please remove the post.
I'm increasingly frustrated with how documentation tooling stinks at striking a balance between being useable for non-technical users and being well suited for automation/compliance workflows. I'm considering putting a service together and have a [quick survey](https://forms.fillout.com/t/aZtDWSYiMrus) that could help me validate some ideas. Also welcome discussion below.
* Why does nobody tackle document localization?
* Why does every service expect data backups to be done with some half-baked manual export function?
* Aside from Confluence, most have no options for data residency.
https://redd.it/1ll6h22
@r_devops
I don't think this breaks community guidelines (I post here regularly), if I am please remove the post.
I'm increasingly frustrated with how documentation tooling stinks at striking a balance between being useable for non-technical users and being well suited for automation/compliance workflows. I'm considering putting a service together and have a [quick survey](https://forms.fillout.com/t/aZtDWSYiMrus) that could help me validate some ideas. Also welcome discussion below.
* Why does nobody tackle document localization?
* Why does every service expect data backups to be done with some half-baked manual export function?
* Aside from Confluence, most have no options for data residency.
https://redd.it/1ll6h22
@r_devops
Doc Survey
Made with Fillout, the best way to make forms, surveys and quizzes your audience will answer.
Bare metal k8s interview questions, what will be asked?
Bare metal k8s interview questions, what will be asked? I said I know bare metal k8s, but Im familiar only cloud managed k8s, What kind of questions can I expect and how to answer them. Can anyone share some insights.
https://redd.it/1ll75yn
@r_devops
Bare metal k8s interview questions, what will be asked? I said I know bare metal k8s, but Im familiar only cloud managed k8s, What kind of questions can I expect and how to answer them. Can anyone share some insights.
https://redd.it/1ll75yn
@r_devops
Reddit
From the devops community on Reddit
Explore this post and more from the devops community
Boss encourages a culture of „fixing in prod“ and it drives me insane
Disclaimer: I’m not a native speaker, I apologize for any confusion.
I’m the „DevOps engineer“ in a kinda established start up (running for more than 6 years, not yet profitable, Series A in October 2023). Technically what we do is not DevOps, rather classic ops just with more chaos but that’s not the topic.
I am responsible of doing the prod deployments and more than half the deployments, it does not go through smoothly. Manual scale downs need to be done before, restarting pods, even sometimes I need to pull in engineers to tell me what’s wrong and then they manually create an index, run a database query or things like that.
After another today if botched deployments today, it pissed me off so much, I wrote a manifesto called „no cowboy ops manifesto“ and here’s the content:
Disclaimer: I used ChatGPT for phrasing but I explicitly fed it my thought before.
**Production is Sacred – Let’s Treat It That Way**
Purpose
We work on live, customer-facing systems. Every action in production reflects our reliability, trustworthiness, and respect for our users. This manifesto defines the **boundaries** we operate within during deployments and incidents.
> “Production is not a playground. It’s a place for professionals who prioritize safety, reliability, and shared responsibility.”
>
## Core Principles
### 1.Rollback First, Investigate Later
If an update breaks, we **roll back within 10 minutes** unless there’s a playbooked fix. Recovery is a process, not a race.
> “Don’t treat rollback as failure. It’s responsible engineering.”
>
### 2. No Manual Fixes Without Audit Trail
No:
- kubectl exec hacks
- Manual scaling or pod deletions
- Ad-hoc DB queries or index creations
- Queue drops or reboots
Unless:
- It’s part of an **approved, version-controlled procedure**
- Actions are **fully logged and explained** in the postmortem
### 3. Every Fix Must Be Reproducible
If it’s not automatable, it’s not production-ready.
Fixes made by hand must be:
- Committed to a Git repo
- Reviewed and explained in plain English
- Deployable via CI/CD
### 4. No Heroes, Only Teams
We value coordinated response over solo acts. If you “save prod” alone:
- You take on **postmortem ownership**
- You also take on **automation follow-up**
- You may still get challenged on why rollback wasn’t used
### 5. Visibility Over Secrecy
Manual interventions will trigger alerts/logs. That’s not to shame—it’s to **protect the system** and learn from every exception.
## **Your Checklist in Production**
- Issue during update? Roll back within 10 minutes.
- Need a manual fix? Stop. Is it versioned or pre-approved?
- Touching prod? Tell the team. No silent SSHs.
- Fixed something? Great. Now write it up and automate it.
Now by boss‘ response was this:
Strongly disagree!
* Generally: When we tell customers we want to do something, we should at all times do everything in our power to ensure that it actually happens. A Rollback means we did not do what we promised to do in a first place and it is for sure considered as failing our promise.
* Priority 1 is always to make an update successful.
We are not in a business where Maintenance windows can be granted multiple times a day or week and this is connected with a huge communication effort on all sides and should be handled very carefully. So if there is any way to proceed even with manual intervention it is encouraged to do whatever needed to be able to make that update a success.
* Rollback should be the last possible solution when everything else failed. Within a maintenance window a rollback can be decided within the last 10 minutes if until that point we were not able to successfully update.
* We should do everything (including Rollback if needed) to be back online before the end of our maintenance window, respecting the window is super important.
* In case we see that we will not hold our maintenance window, we should rollback.In case we need to Rollback, we need to make sure to gather as much information as
Disclaimer: I’m not a native speaker, I apologize for any confusion.
I’m the „DevOps engineer“ in a kinda established start up (running for more than 6 years, not yet profitable, Series A in October 2023). Technically what we do is not DevOps, rather classic ops just with more chaos but that’s not the topic.
I am responsible of doing the prod deployments and more than half the deployments, it does not go through smoothly. Manual scale downs need to be done before, restarting pods, even sometimes I need to pull in engineers to tell me what’s wrong and then they manually create an index, run a database query or things like that.
After another today if botched deployments today, it pissed me off so much, I wrote a manifesto called „no cowboy ops manifesto“ and here’s the content:
Disclaimer: I used ChatGPT for phrasing but I explicitly fed it my thought before.
**Production is Sacred – Let’s Treat It That Way**
Purpose
We work on live, customer-facing systems. Every action in production reflects our reliability, trustworthiness, and respect for our users. This manifesto defines the **boundaries** we operate within during deployments and incidents.
> “Production is not a playground. It’s a place for professionals who prioritize safety, reliability, and shared responsibility.”
>
## Core Principles
### 1.Rollback First, Investigate Later
If an update breaks, we **roll back within 10 minutes** unless there’s a playbooked fix. Recovery is a process, not a race.
> “Don’t treat rollback as failure. It’s responsible engineering.”
>
### 2. No Manual Fixes Without Audit Trail
No:
- kubectl exec hacks
- Manual scaling or pod deletions
- Ad-hoc DB queries or index creations
- Queue drops or reboots
Unless:
- It’s part of an **approved, version-controlled procedure**
- Actions are **fully logged and explained** in the postmortem
### 3. Every Fix Must Be Reproducible
If it’s not automatable, it’s not production-ready.
Fixes made by hand must be:
- Committed to a Git repo
- Reviewed and explained in plain English
- Deployable via CI/CD
### 4. No Heroes, Only Teams
We value coordinated response over solo acts. If you “save prod” alone:
- You take on **postmortem ownership**
- You also take on **automation follow-up**
- You may still get challenged on why rollback wasn’t used
### 5. Visibility Over Secrecy
Manual interventions will trigger alerts/logs. That’s not to shame—it’s to **protect the system** and learn from every exception.
## **Your Checklist in Production**
- Issue during update? Roll back within 10 minutes.
- Need a manual fix? Stop. Is it versioned or pre-approved?
- Touching prod? Tell the team. No silent SSHs.
- Fixed something? Great. Now write it up and automate it.
Now by boss‘ response was this:
Strongly disagree!
* Generally: When we tell customers we want to do something, we should at all times do everything in our power to ensure that it actually happens. A Rollback means we did not do what we promised to do in a first place and it is for sure considered as failing our promise.
* Priority 1 is always to make an update successful.
We are not in a business where Maintenance windows can be granted multiple times a day or week and this is connected with a huge communication effort on all sides and should be handled very carefully. So if there is any way to proceed even with manual intervention it is encouraged to do whatever needed to be able to make that update a success.
* Rollback should be the last possible solution when everything else failed. Within a maintenance window a rollback can be decided within the last 10 minutes if until that point we were not able to successfully update.
* We should do everything (including Rollback if needed) to be back online before the end of our maintenance window, respecting the window is super important.
* In case we see that we will not hold our maintenance window, we should rollback.In case we need to Rollback, we need to make sure to gather as much information as