Is the "DevOps" noscript just becoming a fancy name for a 24/7 Support Engineer?
I’ve been in the industry for some time, and I’m starting to worry about the direction the "DevOps" role is taking in a lot of companies. Originally, it was supposed to be about breaking down silos and shared responsibility, but in many places, it has just turned into a dumping ground for everything the dev team doesn't want to deal with.
If a deployment fails, it’s a DevOps problem. If the cloud bill is too high, it’s a DevOps problem. If a database is slow, call DevOps. We’ve gone from "building platforms" to just being the people who get paged at 3 AM because a noscript we didn't write failed in a way we couldn't predict. We are spending so much time putting out fires that we don't have the bandwidth to actually automate the systems that prevent them.
I’ve been trying to document some better boundaries and automation patterns on OrbonCloud lately.
Are we just stuck as the "everything" engineers now?
https://redd.it/1pyi2tp
@r_devops
I’ve been in the industry for some time, and I’m starting to worry about the direction the "DevOps" role is taking in a lot of companies. Originally, it was supposed to be about breaking down silos and shared responsibility, but in many places, it has just turned into a dumping ground for everything the dev team doesn't want to deal with.
If a deployment fails, it’s a DevOps problem. If the cloud bill is too high, it’s a DevOps problem. If a database is slow, call DevOps. We’ve gone from "building platforms" to just being the people who get paged at 3 AM because a noscript we didn't write failed in a way we couldn't predict. We are spending so much time putting out fires that we don't have the bandwidth to actually automate the systems that prevent them.
I’ve been trying to document some better boundaries and automation patterns on OrbonCloud lately.
Are we just stuck as the "everything" engineers now?
https://redd.it/1pyi2tp
@r_devops
Reddit
From the devops community on Reddit
Explore this post and more from the devops community
Chainguard vs Docker HDI
Docker releasing their hardened images for free - does that affect Chainguard at all or are people fully locked in?
https://redd.it/1pyjhc7
@r_devops
Docker releasing their hardened images for free - does that affect Chainguard at all or are people fully locked in?
https://redd.it/1pyjhc7
@r_devops
Reddit
From the devops community on Reddit
Explore this post and more from the devops community
What's the best way to deploy?
Hi everyone,
I need to deploy a web app ( redmine: an open source project management app). It is an internal Web app.
The app is currently running on a VM with RHEL7 on-prem.
We have over 1000 active users.
We want to use Azure but I really don't know whether I go with Azure App service (container) or Azure Container Apps?
I'll also deploy Azure Files and Azure Database MyDSQL.
I'd appreciate any help or advice.
https://redd.it/1pyjdus
@r_devops
Hi everyone,
I need to deploy a web app ( redmine: an open source project management app). It is an internal Web app.
The app is currently running on a VM with RHEL7 on-prem.
We have over 1000 active users.
We want to use Azure but I really don't know whether I go with Azure App service (container) or Azure Container Apps?
I'll also deploy Azure Files and Azure Database MyDSQL.
I'd appreciate any help or advice.
https://redd.it/1pyjdus
@r_devops
Reddit
From the devops community on Reddit
Explore this post and more from the devops community
I’m building a DevOps simulation, what real-world pain points should I add to make it feel authentic
I wanna build something that for sure nobody is ever going to use but i just hate my free time and i find it intresting enough to build it.
The idea is a game with a similar vibe to Among Us, but aimed at devs / DevOps.
You’re all on the same team, responsible for keeping a company’s software running. One of the players is a saboteur whose goal is to take things down. The rest of the team has to keep production alive and figure out who’s causing the incidents.
The problem: I’m not a real DevOps engineer. I’m a developer who ends up doing DevOps because the companies I work for are too cheap to hire one. So while I know some pain, I’m very aware I probably don’t know half of it.
For now, each round spawns a fresh Ubuntu container that represents the company’s main machine. Every player gets a Linux user on that machine. One player is the “manager” with sudo access and decides who gets elevated privileges and when. The system starts in a working state: applications are already running under a process manager (currently PM2), nginx or Apache is preconfigured (based on player choice), DNS is set up, and there’s a mocked certbot-like setup handling SSL.
For now there are three possible initial system states:
• “Setup by DevOps” – everything is where it’s supposed to be (assuming I didn’t mess anything up).
• “Setup by children” – things mostly work, but there are some mistakes.
• “Setup by a frontend dev” – everything runs as sudo and nothing is where it’s supposed to be.
The game features a in game terminal, browser and some unimportant other apps. The player can interact wiht the pages via the ingame browser and with the machine via the ingame terminal or any terminal and ssh to the container.
Now i am at the stage where i need to make tasks, like "the company changed its name, the website should no longer be www.company.com but www.newcompany.com" and the playes should buy the domain (mocked providers), setup the nameservers and dns records and then nginx. Or change the port of the xBackendService to whatever.
And this is where I’d really appreciate some help: without making it too daunting or frustrating, and while keeping things balanced for both teams, what other DevOps pain points should I add to keep the authenticity, while still making it somewhat fun? (it's a simulation after all and making it really fun would break the immersion i guess)?
PS: i am not trying to advertise this as i am pretty sure it will never go to market. I'm a nerd and just enjoy building interesting things for myself, and this turned out to be surprisingly fun to work on.
https://redd.it/1pym5hv
@r_devops
I wanna build something that for sure nobody is ever going to use but i just hate my free time and i find it intresting enough to build it.
The idea is a game with a similar vibe to Among Us, but aimed at devs / DevOps.
You’re all on the same team, responsible for keeping a company’s software running. One of the players is a saboteur whose goal is to take things down. The rest of the team has to keep production alive and figure out who’s causing the incidents.
The problem: I’m not a real DevOps engineer. I’m a developer who ends up doing DevOps because the companies I work for are too cheap to hire one. So while I know some pain, I’m very aware I probably don’t know half of it.
For now, each round spawns a fresh Ubuntu container that represents the company’s main machine. Every player gets a Linux user on that machine. One player is the “manager” with sudo access and decides who gets elevated privileges and when. The system starts in a working state: applications are already running under a process manager (currently PM2), nginx or Apache is preconfigured (based on player choice), DNS is set up, and there’s a mocked certbot-like setup handling SSL.
For now there are three possible initial system states:
• “Setup by DevOps” – everything is where it’s supposed to be (assuming I didn’t mess anything up).
• “Setup by children” – things mostly work, but there are some mistakes.
• “Setup by a frontend dev” – everything runs as sudo and nothing is where it’s supposed to be.
The game features a in game terminal, browser and some unimportant other apps. The player can interact wiht the pages via the ingame browser and with the machine via the ingame terminal or any terminal and ssh to the container.
Now i am at the stage where i need to make tasks, like "the company changed its name, the website should no longer be www.company.com but www.newcompany.com" and the playes should buy the domain (mocked providers), setup the nameservers and dns records and then nginx. Or change the port of the xBackendService to whatever.
And this is where I’d really appreciate some help: without making it too daunting or frustrating, and while keeping things balanced for both teams, what other DevOps pain points should I add to keep the authenticity, while still making it somewhat fun? (it's a simulation after all and making it really fun would break the immersion i guess)?
PS: i am not trying to advertise this as i am pretty sure it will never go to market. I'm a nerd and just enjoy building interesting things for myself, and this turned out to be surprisingly fun to work on.
https://redd.it/1pym5hv
@r_devops
Reddit
From the devops community on Reddit
Explore this post and more from the devops community
Simple PoW challenge system against AI bots/scrapers of all sorts.
Remember when bots were just annoying? Googlebot, Bingbot, maybe some sketchy SEO crawlers. You'd throw a robots.txt at them and call it a day.
Those days are gone.
Now it's OpenAI, Anthropic, Perplexity, ByteDance, and god knows how many "AI agents" that everyone's suddenly obsessed with. They don't care about robots.txt. They don't care about your bandwidth. They don't care that your home $2/month VPS is getting hammered 24/7 by scrapers training models worth billions.
These companies are scraping content to build AI that will eventually replace the people who created that content. We're literally feeding the machine that's coming for us.
So I built a SHA256 proof-of-work challenge system for Nginx/Openresty. Nothing like Anubis, yet still effective.
https://github.com/terem42/pow-ddos-challenge/
Here's the idea:
Every new visitor solves a small computational puzzle before accessing content
Real browsers with real humans? Barely noticeable — takes <1 second
Scrapers hitting you at scale? Now they need to burn CPU for every single request
At difficulty 5, each request costs \~2 seconds of compute time
Want to scrape 1 million pages? That'll be \~$2,000 in compute costs. Have fun.
The beauty is the economics flip. Instead of YOU paying for their requests, THEY pay for their requests. With their own electricity. Their own CPU cycles.
Yes, if a scraper solves one challenge and saves the cookie, they get a free pass for the session duration. That's why I recommend shorter sessions (POW_EXPIRE=3600) for sensitive APIs.
The economics still work: they need to solve PoW once per IP per session. A botnet with 10,000 IPs still needs 10,000 PoW solutions. It's not perfect, but it's about making scale expensive, not impossible.
It won't stop a determined attacker with deep pockets. Nothing will. But it makes mass scraping economically stupid. And that's really all we can ask for.
https://redd.it/1pylqty
@r_devops
Remember when bots were just annoying? Googlebot, Bingbot, maybe some sketchy SEO crawlers. You'd throw a robots.txt at them and call it a day.
Those days are gone.
Now it's OpenAI, Anthropic, Perplexity, ByteDance, and god knows how many "AI agents" that everyone's suddenly obsessed with. They don't care about robots.txt. They don't care about your bandwidth. They don't care that your home $2/month VPS is getting hammered 24/7 by scrapers training models worth billions.
These companies are scraping content to build AI that will eventually replace the people who created that content. We're literally feeding the machine that's coming for us.
So I built a SHA256 proof-of-work challenge system for Nginx/Openresty. Nothing like Anubis, yet still effective.
https://github.com/terem42/pow-ddos-challenge/
Here's the idea:
Every new visitor solves a small computational puzzle before accessing content
Real browsers with real humans? Barely noticeable — takes <1 second
Scrapers hitting you at scale? Now they need to burn CPU for every single request
At difficulty 5, each request costs \~2 seconds of compute time
Want to scrape 1 million pages? That'll be \~$2,000 in compute costs. Have fun.
The beauty is the economics flip. Instead of YOU paying for their requests, THEY pay for their requests. With their own electricity. Their own CPU cycles.
Yes, if a scraper solves one challenge and saves the cookie, they get a free pass for the session duration. That's why I recommend shorter sessions (POW_EXPIRE=3600) for sensitive APIs.
The economics still work: they need to solve PoW once per IP per session. A botnet with 10,000 IPs still needs 10,000 PoW solutions. It's not perfect, but it's about making scale expensive, not impossible.
It won't stop a determined attacker with deep pockets. Nothing will. But it makes mass scraping economically stupid. And that's really all we can ask for.
https://redd.it/1pylqty
@r_devops
GitHub
terem42/pow-ddos-challenge
A cryptographic proof-of-work challenge system for Nginx/OpenResty that provides robust protection against DDoS attacks, automated scrapers, and AI-powered bots. - terem42/pow-ddos-challenge
We had a credential leak scare and now I do not trust how we share access
"We had a close call last week where an old API key showed up in a place it absolutely should not have been. Nothing bad happened, but it was enough to make me realize how messy our access setup actually is. Between Slack, docs, and password managers, credentials have been shared far more casually than I am comfortable with.
The problem is that people genuinely need access. Contractors, accountants, devs jumping in to help, sometimes even temporary automation. Rotating everything constantly is not realistic, but keeping things as they are feels irresponsible.
I am looking for recommendations on better ways to handle this. Ideally something where access can be granted without exposing credentials and can be revoked instantly without breaking everything else. How are others solving this after a scare like this?"
https://redd.it/1pyo1hh
@r_devops
"We had a close call last week where an old API key showed up in a place it absolutely should not have been. Nothing bad happened, but it was enough to make me realize how messy our access setup actually is. Between Slack, docs, and password managers, credentials have been shared far more casually than I am comfortable with.
The problem is that people genuinely need access. Contractors, accountants, devs jumping in to help, sometimes even temporary automation. Rotating everything constantly is not realistic, but keeping things as they are feels irresponsible.
I am looking for recommendations on better ways to handle this. Ideally something where access can be granted without exposing credentials and can be revoked instantly without breaking everything else. How are others solving this after a scare like this?"
https://redd.it/1pyo1hh
@r_devops
Reddit
From the devops community on Reddit
Explore this post and more from the devops community
are you guys using sop's and runbooks?
i’m about to start writing sops and runbooks for my infra and wanted to see how others are doing it.
are you actually using sops/runbooks in prod or do they just rot over time?
what tools do you use to draft and maintain them?(notion, confluence..)
how are you handling alerts?
would love to hear what setups are actually working (or not) in real companies.
https://redd.it/1pynmxg
@r_devops
i’m about to start writing sops and runbooks for my infra and wanted to see how others are doing it.
are you actually using sops/runbooks in prod or do they just rot over time?
what tools do you use to draft and maintain them?(notion, confluence..)
how are you handling alerts?
would love to hear what setups are actually working (or not) in real companies.
https://redd.it/1pynmxg
@r_devops
Reddit
From the devops community on Reddit
Explore this post and more from the devops community
How do you enforce escalation processes across teams?
In environments with multiple teams and external dependencies, how do you enforce that escalation processes are actually respected?
Specifically:
* required inputs are always provided
* ownership is clear
* escalations don’t rely on calls or tribal knowledge
Or does it still mostly depend on people chasing others on Slack?
Looking for real experiences, not theoretical frameworks.
https://redd.it/1pynic2
@r_devops
In environments with multiple teams and external dependencies, how do you enforce that escalation processes are actually respected?
Specifically:
* required inputs are always provided
* ownership is clear
* escalations don’t rely on calls or tribal knowledge
Or does it still mostly depend on people chasing others on Slack?
Looking for real experiences, not theoretical frameworks.
https://redd.it/1pynic2
@r_devops
Reddit
From the devops community on Reddit
Explore this post and more from the devops community
how to combine 2 different framework in devops temple
ok guys I know it's not make sense.
1) english is not my first language
2)I am not a devops professional. just practicing
so I want to set up a wordpress app to write blog posts (I already host one wordpress on my ec2 so I am familiar with wordpress little bit ) and I have another app as side project and want to set a cd/ci pipeline for my side project and I want to post progress of my side project in the blog but where I am struggle is:
1) wordpress written in php and different framework, my side project written in java with springboot. is it common to interact 2 different framework ?
2) I want to keep my wordpress container up always, would it cost too much ?
3) is it make sense to host my wordpress as container?
https://redd.it/1pytdp5
@r_devops
ok guys I know it's not make sense.
1) english is not my first language
2)I am not a devops professional. just practicing
so I want to set up a wordpress app to write blog posts (I already host one wordpress on my ec2 so I am familiar with wordpress little bit ) and I have another app as side project and want to set a cd/ci pipeline for my side project and I want to post progress of my side project in the blog but where I am struggle is:
1) wordpress written in php and different framework, my side project written in java with springboot. is it common to interact 2 different framework ?
2) I want to keep my wordpress container up always, would it cost too much ?
3) is it make sense to host my wordpress as container?
https://redd.it/1pytdp5
@r_devops
Reddit
From the devops community on Reddit
Explore this post and more from the devops community
How much code are you writing daily
what's is the dev ops workflow like. are you always writing automation noscripts or is a large chunk reviewing others noscripts. how much of the job are you actually writing noscripts. And what is the best advice you can give me with becoming a dev ops engineer. what do you feel you really need to understand to make it in the field.
https://redd.it/1pyx2x1
@r_devops
what's is the dev ops workflow like. are you always writing automation noscripts or is a large chunk reviewing others noscripts. how much of the job are you actually writing noscripts. And what is the best advice you can give me with becoming a dev ops engineer. what do you feel you really need to understand to make it in the field.
https://redd.it/1pyx2x1
@r_devops
Reddit
From the devops community on Reddit
Explore this post and more from the devops community
Devops free courses
Can you guys recommend free courses,I know that DevOps it's plenty of tools, skills, recommend me please good docker,terraform etc.. Thanks.
https://redd.it/1pyyyzz
@r_devops
Can you guys recommend free courses,I know that DevOps it's plenty of tools, skills, recommend me please good docker,terraform etc.. Thanks.
https://redd.it/1pyyyzz
@r_devops
Reddit
From the devops community on Reddit
Explore this post and more from the devops community
Thinking About a DevOps Career in 2026? Focus on What Truly Counts
A lot of beginners jump straight into Docker and Kubernetes, only to feel overwhelmed a few weeks later. That confusion is normal. DevOps is not about memorizing a checklist of tools. It is about understanding systems, building the right habits, and introducing tools only when they actually solve a problem.
If I were starting from scratch in 2026, this is the approach I would follow.
# 1. Start With Strong Foundations
Before automating anything, you must understand what you are automating.
Spend time on:
Linux fundamentals like file systems, processes, permissions, and services
Networking basics such as IP addressing, DNS, HTTP/HTTPS, ports, routing, NAT, and firewalls
Core system administration concepts including users, groups, packages, and logs
Bash noscripting for day-to-day automation
Basic Python for tasks like API calls, log parsing, and simple automation
If you cannot clearly explain what happens when you run a `curl` command or why a service fails to start, advanced tools will only add confusion later.
# 2. Git and CI/CD Are Non-Negotiable
Version control sits at the heart of DevOps. Get comfortable with Git concepts like branching, pull requests, merges, and conflict resolution.
After that, move into CI/CD. Tools may vary, but the concepts stay the same:
Jenkins
GitLab CI
GitHub Actions
CircleCI
Do not treat pipelines as magic buttons. Learn how stages work, how tests run, how artifacts are created, and what a proper rollback looks like when something breaks.
# 3. Containers, Then Orchestration
Containers matter, but timing matters too.
Start with Docker:
Write Dockerfiles
Understand images and layers
Use volumes and networks
Run multi-service setups with Docker Compose
Only once this feels natural should you move to Kubernetes. Take it slow and focus on:
Pods, deployments, and services
ConfigMaps and secrets
Scaling and rolling updates
Ingress and service discovery
You should also get familiar with managed Kubernetes platforms like EKS, AKS, or GKE.
# 4. Cloud Knowledge Is Mandatory
Pick one cloud provider and go deep. AWS is common, but Azure or GCP are equally valid depending on your region.
Core areas to learn:
Compute services
Virtual networking and security boundaries
Object and block storage
Identity and access management with least-privilege principles
Once comfortable, practice deploying containerized or Kubernetes workloads in the cloud.
# 5. Infrastructure as Code
Manual cloud setups do not scale. Infrastructure must be repeatable and version-controlled.
Terraform is a solid starting point. Learn how to:
Define resources using code
Use variables and modules properly
Apply and destroy infrastructure safely
Manage and secure remote state
# 6. Observability: Metrics, Logs, Alerts
If you cannot see failures, you cannot operate systems.
Get practical experience with:
Metrics using Prometheus and Grafana
Centralized logging with tools like the ELK stack
Cloud-native monitoring solutions such as CloudWatch
Understanding what “healthy” looks like is just as important as knowing when things break.
# 7. Security as a Default Practice
Security is no longer optional in DevOps.
Learn the basics of:
Vulnerability scanning for code and containers
Secure secret management
Hardening Docker images
Applying IAM best practices
These skills naturally lead into DevSecOps responsibilities.
# 8. Build End-to-End Projects
Tutorials help, but real learning happens when you build something complete.
Good project ideas include:
A microservice-based application using Docker
A full CI/CD flow from commit to cloud deployment
Infrastructure provisioning using Terraform
Monitoring and logging integrated into the system
Document everything clearly in GitHub so others can understand your decisions.
# 9. Learn With the Community
DevOps is collaborative by nature. Learning in isolation slows you down.
Join DevOps communities
A lot of beginners jump straight into Docker and Kubernetes, only to feel overwhelmed a few weeks later. That confusion is normal. DevOps is not about memorizing a checklist of tools. It is about understanding systems, building the right habits, and introducing tools only when they actually solve a problem.
If I were starting from scratch in 2026, this is the approach I would follow.
# 1. Start With Strong Foundations
Before automating anything, you must understand what you are automating.
Spend time on:
Linux fundamentals like file systems, processes, permissions, and services
Networking basics such as IP addressing, DNS, HTTP/HTTPS, ports, routing, NAT, and firewalls
Core system administration concepts including users, groups, packages, and logs
Bash noscripting for day-to-day automation
Basic Python for tasks like API calls, log parsing, and simple automation
If you cannot clearly explain what happens when you run a `curl` command or why a service fails to start, advanced tools will only add confusion later.
# 2. Git and CI/CD Are Non-Negotiable
Version control sits at the heart of DevOps. Get comfortable with Git concepts like branching, pull requests, merges, and conflict resolution.
After that, move into CI/CD. Tools may vary, but the concepts stay the same:
Jenkins
GitLab CI
GitHub Actions
CircleCI
Do not treat pipelines as magic buttons. Learn how stages work, how tests run, how artifacts are created, and what a proper rollback looks like when something breaks.
# 3. Containers, Then Orchestration
Containers matter, but timing matters too.
Start with Docker:
Write Dockerfiles
Understand images and layers
Use volumes and networks
Run multi-service setups with Docker Compose
Only once this feels natural should you move to Kubernetes. Take it slow and focus on:
Pods, deployments, and services
ConfigMaps and secrets
Scaling and rolling updates
Ingress and service discovery
You should also get familiar with managed Kubernetes platforms like EKS, AKS, or GKE.
# 4. Cloud Knowledge Is Mandatory
Pick one cloud provider and go deep. AWS is common, but Azure or GCP are equally valid depending on your region.
Core areas to learn:
Compute services
Virtual networking and security boundaries
Object and block storage
Identity and access management with least-privilege principles
Once comfortable, practice deploying containerized or Kubernetes workloads in the cloud.
# 5. Infrastructure as Code
Manual cloud setups do not scale. Infrastructure must be repeatable and version-controlled.
Terraform is a solid starting point. Learn how to:
Define resources using code
Use variables and modules properly
Apply and destroy infrastructure safely
Manage and secure remote state
# 6. Observability: Metrics, Logs, Alerts
If you cannot see failures, you cannot operate systems.
Get practical experience with:
Metrics using Prometheus and Grafana
Centralized logging with tools like the ELK stack
Cloud-native monitoring solutions such as CloudWatch
Understanding what “healthy” looks like is just as important as knowing when things break.
# 7. Security as a Default Practice
Security is no longer optional in DevOps.
Learn the basics of:
Vulnerability scanning for code and containers
Secure secret management
Hardening Docker images
Applying IAM best practices
These skills naturally lead into DevSecOps responsibilities.
# 8. Build End-to-End Projects
Tutorials help, but real learning happens when you build something complete.
Good project ideas include:
A microservice-based application using Docker
A full CI/CD flow from commit to cloud deployment
Infrastructure provisioning using Terraform
Monitoring and logging integrated into the system
Document everything clearly in GitHub so others can understand your decisions.
# 9. Learn With the Community
DevOps is collaborative by nature. Learning in isolation slows you down.
Join DevOps communities
like:
Reddit (r/devops, r/kubernetes, r/aws, r/sre)
CNCF Slack channels
DevOps Discord servers
Local meetups or conferences
Online tech communities that are oriented towards Cloud and Devops (hexplain.space)
# 10. Be Consistent, Not Overwhelmed
DevOps is a long-term journey. Tools will change, fundamentals will not.
If you dedicate a few focused hours each week and build your skills layer by layer, becoming job-ready within several months is realistic. The key is patience, consistency, and learning with purpose.
Join the conversation, stay curious, and keep building.
https://redd.it/1pzalqb
@r_devops
Reddit (r/devops, r/kubernetes, r/aws, r/sre)
CNCF Slack channels
DevOps Discord servers
Local meetups or conferences
Online tech communities that are oriented towards Cloud and Devops (hexplain.space)
# 10. Be Consistent, Not Overwhelmed
DevOps is a long-term journey. Tools will change, fundamentals will not.
If you dedicate a few focused hours each week and build your skills layer by layer, becoming job-ready within several months is realistic. The key is patience, consistency, and learning with purpose.
Join the conversation, stay curious, and keep building.
https://redd.it/1pzalqb
@r_devops
Reddit
Everything DevOps
r/devops
Supply chain feels “unfinished” once things are live
We do all the right things at build time, but I’ve still seen dependencies behave oddly once they’re under real traffic.
It made me realize how much we assume build-time checks are enough.
How are others thinking about this after deployment?
https://redd.it/1pz9xn9
@r_devops
We do all the right things at build time, but I’ve still seen dependencies behave oddly once they’re under real traffic.
It made me realize how much we assume build-time checks are enough.
How are others thinking about this after deployment?
https://redd.it/1pz9xn9
@r_devops
Reddit
From the devops community on Reddit
Explore this post and more from the devops community
CKAD exam pricing confusion: KodeKloud vs Linux Foundation
I recently purchased CKAD via KodeKloud.
For my other four Kubernetes certifications, I bought the exams directly from the Linux Foundation, but this time KodeKloud was offering 55% off for annual subscribers.
https://preview.redd.it/88jby84yo9ag1.png?width=1386&format=png&auto=webp&s=7d94cdcacfd9db0e6f1fced2aca6ddbd500a36b3
The main reason I purchased the annual subnoscription was to use this discount when needed. After applying it, I paid ₹20.5k INR (including taxes).
Once I redeemed the voucher, it showed:
>
That was fine with me, as I was confident I won’t need a retake.
However, today I accidentally landed on this Linux Foundation page:
https://trainingportal.linuxfoundation.org/learn/course/certified-kubernetes-application-developer-single-attempt-ckad-single/exam/exam
It lists the same CKAD single-attempt exam for $140 (\~₹12–12.5k INR).
https://preview.redd.it/zx7tz4u0p9ag1.png?width=1391&format=png&auto=webp&s=04a80c160758b3dd3eafdcd2ac002de7600b51fe
Same exam.
Same attempt type.
Different platforms. Very different prices.
Am I missing something here or is this just confusing / misleading discount framing?
Posting this to understand better and to help others make an informed choice.
https://redd.it/1pz89eo
@r_devops
I recently purchased CKAD via KodeKloud.
For my other four Kubernetes certifications, I bought the exams directly from the Linux Foundation, but this time KodeKloud was offering 55% off for annual subscribers.
https://preview.redd.it/88jby84yo9ag1.png?width=1386&format=png&auto=webp&s=7d94cdcacfd9db0e6f1fced2aca6ddbd500a36b3
The main reason I purchased the annual subnoscription was to use this discount when needed. After applying it, I paid ₹20.5k INR (including taxes).
Once I redeemed the voucher, it showed:
>
That was fine with me, as I was confident I won’t need a retake.
However, today I accidentally landed on this Linux Foundation page:
https://trainingportal.linuxfoundation.org/learn/course/certified-kubernetes-application-developer-single-attempt-ckad-single/exam/exam
It lists the same CKAD single-attempt exam for $140 (\~₹12–12.5k INR).
https://preview.redd.it/zx7tz4u0p9ag1.png?width=1391&format=png&auto=webp&s=04a80c160758b3dd3eafdcd2ac002de7600b51fe
Same exam.
Same attempt type.
Different platforms. Very different prices.
Am I missing something here or is this just confusing / misleading discount framing?
Posting this to understand better and to help others make an informed choice.
https://redd.it/1pz89eo
@r_devops
The hardest incidents to explain are the quiet ones
Some of the hardest security incidents I’ve been part of weren’t dramatic. No outages, no obvious alerts, nothing screaming for attention.
Just small things that didn’t line up in hindsight.
How do you all validate concerns when there’s no clear signal yet?
https://redd.it/1pzcww5
@r_devops
Some of the hardest security incidents I’ve been part of weren’t dramatic. No outages, no obvious alerts, nothing screaming for attention.
Just small things that didn’t line up in hindsight.
How do you all validate concerns when there’s no clear signal yet?
https://redd.it/1pzcww5
@r_devops
Reddit
From the devops community on Reddit
Explore this post and more from the devops community
zsh-doppler - ZSH plugin to show Doppler project/config in your prompt
I work with a lot of Doppler projects and got tired of running doppler setup / configure to remember which env I was in. So I made a simple plugin that shows [project/config\] in your prompt.
Colors change based on environment - green for dev, yellow for staging, red for prod. Helps avoid that "oh shit" moment when you realize you were in prod.
Works with Oh My Zsh, Powerlevel10k, zinit, etc.
https://github.com/lsdcapital/zsh-doppler
Contributions welcome, happy to help debug, improve it based on feedback
https://redd.it/1pzdt6a
@r_devops
I work with a lot of Doppler projects and got tired of running doppler setup / configure to remember which env I was in. So I made a simple plugin that shows [project/config\] in your prompt.
Colors change based on environment - green for dev, yellow for staging, red for prod. Helps avoid that "oh shit" moment when you realize you were in prod.
Works with Oh My Zsh, Powerlevel10k, zinit, etc.
https://github.com/lsdcapital/zsh-doppler
Contributions welcome, happy to help debug, improve it based on feedback
https://redd.it/1pzdt6a
@r_devops
GitHub
GitHub - lsdcapital/zsh-doppler: Zsh plugin that displays your current doppler environment in the prompt
Zsh plugin that displays your current doppler environment in the prompt - lsdcapital/zsh-doppler