270
Reddit DevOps. #devops Thanks @reddit2telegram and @r_channels
What bottlenecks still prevent teams from achieving much higher productivity across projects?
In theory, integrating Slack, Notion, Linear, GitHub, Google Drive, CRM, email, and databases should create a shared work environment with sustained context.
In practice, What bottlenecks still prevent teams from achieving much higher productivity across projects?
https://redd.it/1tgrrwn
@r_devops
Ephemeral Environment
Really looking for advice or tips on how others have handled this setup.
We need to spin up ephemeral environments whenever a release PR is opened (specifically from UAT → master). Our goal is to run end to end tests in these environments as part of release validation, plus also support manual testing and nightly runs. And perform cleanup after tests.
Our current stack looks like this:
Jenkins
Kubernetes
ArgoCD
Kustomize
Gitea
One major constraint is that I don’t have full cluster access we’re restricted to a single namespace only.
Has anyone implemented something similar under these limitations? How did you structure your ephemeral environments, especially with ArgoCD + limited Kubernetes permissions?
Any patterns, tooling approaches, or lessons learned would really help.
https://redd.it/1tgsjel
@r_devops
Multi-agent AI code review: 17 of 18 findings false. Lessons from burning credits
I've been personally experimenting with multi-agent code review: separate specialist agents for security, implementation, testing, and architecture, running them on every PR I open. On one last month, 18 findings reported, only 1 survived manual verification.
The failure modes were consistent:
- Agents flagged files that weren't in the diff at all.
- "code does X" claims without quoting the offending line.
- Functions read in isolation, missing upstream guards.
- Pre-existing patterns flagged as PR-introduced.
What stuck: a triage step before dispatching specialists. It pulls the + line list from gh pr diff, builds a small context bundle (changed files, repo conventions, analogous code), and picks which specialists to run based on PR size and surface. Docs-only? Skip security and architecture. Multi-file change touching auth? All four. Specialists must then quote the offending line for any finding they raise; if they can't, it's dropped before reaching me.
I haven't wired this into CI yet, but the triage step would slot in cleanly as a pre-merge check.
If you're running AI review on real PRs, how are you bounding the false-positive rate? Per-agent diff scope, post-hoc filtering, or something else?
https://redd.it/1tgpnfb
@r_devops
Graduating this year and want to start DevOps/Cloud Engineering — where should I begin?
​
Hey everyone, I’m graduating this year and I want to build my career in DevOps/Cloud Engineering. Right now I’m learning Python basics and trying to understand what roadmap I should follow next.
I’m confused whether I should:
Learn from YouTube/free resources first
Join an online/offline course later
Focus on Cloud (AWS/Azure/GCP) directly or first build strong fundamentals
Can anyone suggest:
A good beginner roadmap for DevOps/Cloud
Best YouTube channels/playlists to follow
Platforms/courses that are actually worth it
Skills I should focus on first (Linux, Networking, Docker, Git, AWS, etc.)
I’d really appreciate advice from people already working in DevOps/Cloud. Thanks!
https://redd.it/1tgjfc9
@r_devops
What does actual devops engineer do
Rn,im doing devops. But GODDAMN its boring. I create pipeline, have it build,obfuscate,orchestrate stuff,bla bla,but when its time to run/test my work,its almost 2 hrs per run. While its running,i do nothing. Yes,i do study, when doing nothing,but it gets boring. If only my table is at a better location, i wudve run netflix (without earbuds). Is this a normal thing in devops? or is it normal in the devops field. Btw im in a small software company, so workload on my end is mostly light, medium at best.
https://redd.it/1tgg27v
@r_devops
Launching a pilot soon and a Bit Overwhelmed.
I began my project as a cybersecurity evidence and 3rd party secure access platform that sits above existing security for those times cases are elevated and the process becomes part of the risk. But I came to the conclusion that my thinking was too narrow.
I had built the truth core first and only the terminology was cyber specific. So I changed direction. I made the truth core a general evidence handler with secure 3rd party derivative sharing and disclosure platform. I then created a cyber pack, an insurance pack, an HR pack, and a legal pack. The workflow, UI/UX, webhooks needed, etc. is individualized for each industry, but all run on the some core.
Now I can license each individually or license the core engine to teams building investigation software who need infrastructure. I can add as many industry packs as I want without altering the core. If I want new global functions I can alter the core without rebuilding the packs.
Starting the pilot in 6 weeks. And I am damn proud of myself since I built this solo. But I would love some advice on what to look out for during the pilot. It's uncharted waters for me.
(https://www.reddit.com/submit/?sourceid=t31tg3f01&composerentry=crosspostprompt)
https://redd.it/1tg7acb
@r_devops
Launching a Pilot seen....nervous
I began my project as a cybersecurity evidence and 3rd party secure access platform that sits above existing security for those times cases are elevated and the process becomes part of the risk. But I came to the conclusion that my thinking was too narrow.
I had built the truth core first and only the terminology was cyber specific. So I changed direction. I made the truth core a general evidence handler with secure 3rd party derivative sharing and disclosure platform. I then created a cyber pack, an insurance pack, an HR pack, and a legal pack. The workflow, UI/UX, webhooks needed, etc. is individualized for each industry, but all run on the some core.
Now I can license each individually or license the core engine to teams building investigation software who need infrastructure. I can add as many industry packs as I want without altering the core. If I want new global functions I can alter the core without rebuilding the packs.
Starting the pilot in 6 weeks. And I am damn proud of myself since I built this solo. But I would love some advice on what to look out for during the pilot. It's uncharted waters for me.
https://redd.it/1tfvzl0
@r_devops
Criticed to be better
Hi I am a devops engineer who is too comfortable in his position and wanted to push out of the comfort zone.I love to make application and then test it in different stress environment and watch it be handle its intended design.
I have heard in some companies when new hires that are to be promoted they are encouraged to make app and then s/he is asked bunch of question about it architectural choices by the seniors I wanted to try that and understand my shortcomings and make my app durable.
Is there any discord server or Reddit where we can post our design and get criticized but with growth mindset . Just sharing knowledge and experience ?
https://redd.it/1tfq26q
@r_devops
Removed by Reddit
Removed by Reddit on account of violating the [content policy. ]
https://redd.it/1tfkqp5
@r_devops
How do you handle security/monitoring of Claude Code in your workplace?
We're considering deploying Claude Code to our development team, but our security team has concerns.
Specifically:
\- How do you monitor what Claude Code does on employee machines?
\- Do you have visibility into the APIs it calls?
\- How do you handle compliance/audit requirements?
Has anyone dealt with this? Would love to hear how other companies are approaching this problem.
https://redd.it/1tfkifp
@r_devops
Runbooks survive rotation changes. A lot of actual incident knowledge doesn’t.
One thing I've noticed after rotation changes is that all the runbooks, dashboards, alerts, postmortems.… They're still there.
But what often disappears? The undocumented filter logic people develop over time. Like which alerts are usually just noise and can be ignored. Which metrics spike with every deploy but don’t actually mean anything’s wrong. Which services look suspicious at first glance but just overthought in reality.
And which checks waste 20 minutes every time because they lead to dead ends.
There's always a few folks on each rotation who handle incidents faster than others, because they've seen the same failure pattern before and *already* know not to go down those useless paths.
you’d have one engineer leave and nobody realized how much of that knowledge lived only in their head until later, so the same incidents would keep happening with the same tools available… but resolution took way longer this time around since everyone defaulted back to obvious routes first instead of cutting straight through like she used to do automatically from experience alone.
https://redd.it/1tfh8hc
@r_devops
shipcheck: static scanner for AI-generated code, focused on the patterns AI agents actually introduce
AI coding tools have consistent and predictable security failure modes. After seeing the same issues repeatedly I built a scanner specifically targeting them.
20 rules covering: hardcoded secrets across major providers, SQL injection via string concatenation, shell injection, wildcard CORS, SSL verification disabled, debug mode left on, NEXT_PUBLIC_ secret exposure, hallucinated package names, pinned packages with known CVEs, and deferred security TODOs.
Everything is a regex or AST check. No LLM involved. Bundled CVE list means no network call required. Integrates into CI with --json --fail-on=high.
https://www.shipcheck.space/
https://redd.it/1tf4jic
@r_devops
What's the actual cost of severity inflation across a 6-month backlog?
Been thinking about this a lot lately and I don't see it discussed enough.
Everyone talks about severity inflation as an annoyance engineers file everything Critical, the priority column becomes noise, PMs re-rank manually before every sprint. Frustrating, sure. But the actual cost runs deeper than lost time in sprint planning.
Here's what I think is actually happening over 6 months of inflated priorities:
You're shipping the wrong things. When everything is Critical, nothing is. The bugs that actually hurt paying customers the ones that silently corrupt data, that block key workflows, that churn enterprise accounts get lost in a sea of P1s filed by engineers who just wanted their ticket looked at.
Your backlog stops being a planning tool. After a few sprints of political triage, the backlog reflects who complained loudest, not what matters. At that point it's not a backlog it's a graveyard with bad metadata.
Stakeholder trust erodes. Sales stops believing the PM's priority calls because they've seen them get overridden. Engineering stops caring about severity labels because they know they're meaningless. Everyone stops using the system as intended and starts working around it.
The compounding effect: each sprint of bad triage makes the next one harder. You inherit the previous sprint's inflated backlog on top of new tickets. The signal-to-noise ratio gets worse over time, not better.
Curious if anyone has tried to actually quantify this, either the time cost or the downstream impact on retention or churn. Or is this just something teams accept as background noise?
https://redd.it/1tez36v
@r_devops
DevOps Mentorship / Sharing experience
Hi everyone. I’m a QA Engineer with 5+ years of experience and 3+ years as a Release Manager. Because of my release management background, I became really interested in moving into DevOps.
I’ve already finished a general DevOps course, but I still feel like I’m missing understanding of real-world practices and what I should focus on next.
So now I’m looking for someone who could share some advice, experience, or maybe mentor me a bit during this transition.
I’d really appreciate any help or guidance
Any advice in comments about what pet-project should I build to gain more experience/confidence will be appreciated!
Thanks
https://redd.it/1tetp12
@r_devops
How low should someone go to get jobs faster?
In freelancing, How low should a fixed rate or hourly rate be if i want to get jobs faster? For an entry level person.
https://redd.it/1term1c
@r_devops
How extensively do you use the install- actions?
Hey everyone!
In the context of all the previous github actions compromissions, I'm strongly reducing the amount of different actions we use in my company.
What's your take on the install-\ actions, like install-poetry, setup-terraform, setup-trivy etc.? Otherwise, do you manually install them with curl commands? Or use tools like mise-en-place?
What are your strategies to reduce 3rd party exposition?
Cheers!
https://redd.it/1tgrvgg
@r_devops
Sidney Dekker's (safety researcher) point of views applied to AI SRE agents
Hi all,
We've been studying Sidney Dekker's safety research in the context of recent developments in the AI agents space (PS: we do build in this space!) and how they map to devops, SRE, infrastructure engineering.
Some things we learned that were helpful of how we would run post-incident scenarios differently:
1/ Old view vs New view. These are the two worlds he split the debate into. The old view says the system is fine, so find the one, the person who messed up. The new view says people act in ways that made sense given the info, goals and pressure they had. Sidney Dekker refers to that in his book as local rationality and applied to AI i.e. an agent has local rationality too, just on a different base.
2/ "Bad model" is old-view thinking. When an agent makes a confident wrong call, the useful question is what the system fed it and what it was optimising for - goals are important and we have to look at it from that lens and consider the model to be an entity who messed up.
3/ This pattern isn't new. Lisanne Bainbridge (we learned about her during this research; fascinating story and worth checking out) also wrote this in her paper Ironies of Automation in 1983 where she said that the failure pattern was discovered and labeled decades before the tooling existed. IMO, that just shows that it is a known category, not a surprise.
4/ Agent drift is 100% the real risk. All of us have seen the agent following the directions rationally and locally do the right thing but in production it goes horribly wrong.
5/ Keep humans in the reps. IMO, the danger is never that agent is wrong once or twice, it is the essentially team losing the ability to be right on the incident that the agent has never seen. That's exactly why you are deploying agents, right?
Thought we'd share the perspectives of some old stalwarts and in this really fast moving field. Hope it helps.
https://redd.it/1tguqc6
@r_devops
Looking for someone to learn Kubernetes, Terraform, GCP
Hey everyone,
I'm looking for someone to learn and improve DevOps skills with. I've been learning things like Kubernetes, Python, and GCP, and I think it would be great to have someone to study with, share knowledge, and maybe build some small projects together.
A little bit about me. I’ve been working as a DevOps Engineer in one company for around 3 years. I feel a bit stuck right now, not because of laziness, but mostly because there aren’t many opportunities to grow in my current job. Most of the time I work on CI/CD pipelines, write some Ansible playbooks, connect Spring applications with tools like Graylog and Prometheus, and at the end of the process we mainly use Docker.
I'd really like to grow more in Kubernetes, ArgoCD, and GCP. I'm also looking for ideas on how to create more real-world scenarios and practical projects to improve my skills. If you have suggestions about what I should focus on or learn next, I'd really appreciate it.
My goal is to go from zero to hero in modern DevOps/cloud technologies.
If anyone is interested in learning together, feel free to comment or send me a DM.
https://redd.it/1tgn0pn
@r_devops
DevOps Monitoring tool
https://uptime.nepsesignal.com
https://redd.it/1tgh688
@r_devops
Weekly Self Promotion Thread
Hey r/devops, welcome to our weekly self-promotion thread!
Feel free to use this thread to promote any projects, ideas, or any repos you're wanting to share. Please keep in mind that we ask you to stay friendly, civil, and adhere to the subreddit rules!
https://redd.it/1tge7pj
@r_devops
Career pivot from bare metal infra to DevOps
Hi, I'm in my first real IT role infrastructure engineer role at a hosting company. Before this I was more on the telecom and hardware side, so the past couple of months have been a steep learning curve. I've picked up a lot: managing large fleets of bare-metal servers, virtualization, setting up monitoring for infra(Telegraf, Grafana), Ansible automation, and some security tooling. But mainly with the help of AI tools.
What I'm missing: Kubernetes (zero experience), CI/CD pipelines, cloud platforms (AWS/Azure), and Terraform. Basically everything the "DevOps" job market seems to want.
Some days I feel like I'm growing fast. Other days I feel drained there's a lot to absorb. Just want to know if I'm headed in the right direction or wasting time.
Anyone made a similar transition? What would you prioritize first?
https://redd.it/1tg3zbd
@r_devops
MCP server that lets AI agents query Grafana Loki logs and speed-up debugging issues
I've created an MCP server that gives AI agents access to Grafana Loki logs - and here's how it compares to the official one
GitHub: https://github.com/incu6us/loki-mcp-server
The problem: AI assistants are great at debugging, but they can't access your logs. Observability data lives in Loki, while AI operates without that context.
This project bridges that gap by exposing Loki through MCP, so an AI agent can run LogQL queries directly.
Example prompt:
Find errors from payment-service in the last 30 minutes using loki mcp server
The agent queries Loki, gets the logs, and can then analyze them, summarize the incident, or suggest root causes.
# How it differs from Grafana's implementations
Grafana has two official options: `grafana/loki-mcp` (standalone Loki MCP) and `grafana/mcp-grafana` (unified Grafana MCP with 70+ tools). Here's where my project takes a different approach:
|Name|loki-mcp-server (this project)|grafana/loki-mcp|grafana/mcp-grafana|
|:-|:-|:-|:-|
|Tools|5 granular tools: query, query_range, labels, label_values, series|loki_query \+ labels (added in v0.5.0)|5 Loki tools + patterns + stats (70+ total)|
|Design philosophy|Discovery-first - agent explores labels/series before building queries|Query-first - agent must already know the schema|Full Grafana ecosystem|
|Connection|Direct to Loki API|Direct to Loki API|Through Grafana datasource proxy (requires Grafana)|
|Auth|Basic auth, Bearer token, multi-tenant (X-Scope-OrgID)|Basic auth, Bearer token, org ID|Grafana RBAC|
|Transport|stdio|stdio, SSE, streamable HTTP|stdio|
|Input validation|Strict - limit caps (max 5000), direction validation, label format checks|Basic|Basic|
|Install|Homebrew, go install, binary|Binary, Docker|Binary|
The key difference is the discovery-first approach. LLMs don't always know your label schema upfront. With 5 separate tools, the agent can:
1. Call labels to see what's available
2. Call label_values to explore specific labels
3. Call series to find active streams
4. Build a precise query or query_range based on what it discovered
This matters because a model guessing at label names generates bad LogQL and wastes tokens on retries. Letting it discover the schema first leads to better queries on the first attempt.
# Use cases
AI-assisted debugging and root cause analysis
Automated incident investigation
Log summarization and pattern detection
DevOps observability automation
Looking for feedback from people using Loki, MCP, or AI agents in DevOps workflows. Ideas for improvements, integrations, or features are welcome.
https://redd.it/1tfs3s6
@r_devops
Q: Manageable build/test environments - how?
Folks, when you have to build and test native for all 3 OS - how you managing your environments?
For just linux it's kind-of obvious, but I had to support MacOS, Linux and Windows and they are constantly broken due to configuration drift and previous build state failure. So how you manage those? Or you already switched to SaaS platforms like pushed hard by marketing teams GH Actions?
https://redd.it/1tfq489
@r_devops
A Beginner’s Dilemma: Navigating the path between DevOps, Cloud, and Development backgrounds
Hi r/DevOps,
I am a beginner looking to enter the industry, but I'm currently feeling quite confused about the relationship—and the differences—between DevOps and Cloud.
Initially, my goal was to jump directly into the Cloud field. However, after doing some research, I learned that Cloud Engineering isn't typically an entry-level role. Most advice suggested that I need a strong foundation in DevOps first and that working in Cloud requires significant prior experience.
So, I adjusted my plan and decided to start learning DevOps. But this led me to another roadblock. I was told that to have a real chance in DevOps, I need to be excellent at Linux, and that DevOps also isn't very friendly to beginners. It feels like a career ladder where you need prior experience.
For example, I've noticed people saying you need a background in software/application development (like Frontend or Backend) to have a strong chance. The logic is that you need to fully understand the code's lifecycle from development all the way through to operations.
Because of all this, I have a few specific questions:
1. The Entry Path: What is the difference between mastering Linux to enter DevOps directly versus transitioning into DevOps from a Software Development background?
2. Job Prospects: Are my chances of landing a job significantly weaker if I strictly focus on Linux/Ops skills without coming from a pure development background?
3. The Career Ladder: Do I absolutely need to go through DevOps first in order to eventually reach a Cloud Engineering role?
I realize my thoughts might be a bit scattered and I might have some misconceptions, but I would really appreciate it if some experienced professionals here could help clear things up for me.
Thank you in advance!
https://redd.it/1tfl0go
@r_devops
What actually gets lost when on-call rotates isn’t in the runbooks
When you're handing off on-call? The runbook covers the basics: where the dashboards are, who to page if something’s really bad… all that standard stuff.
But there's this other layer, the things you actually say when passing it on. Like:
\- "Hey, if Alert X fires up? Everyone thinks ‘check Y,’ but don’t bother with Y at all. Just go straight to Z."
\- "If logging for Service A stops suddenly? Usually not a logging problem at all, something upstream probably died quietly."
That kind of info gets shared in conversations during handoffs but not documented anywhere official.
You say it once while sitting across from someone and hope they remember later... because if they roll off rotation soon after? That knowledge just evaporates
https://redd.it/1tfhspf
@r_devops
Is DevOps a “meaningful” career?
Hey devs,
Do you feel your work is meaningful enough to justify the effort you put in it?
Maybe one of your projects contributes to life-saving impact, or quietly powers logistics systems that keep our food supply moving, or even on a smaller level simply saves consumers’ time.
bonus: If yes, what kind of metrics would you measure to justify it as “positive impact”?
https://redd.it/1tf8edb
@r_devops
That nginx 18 year vuln has me rethinking how we review infra code
So an AI found CVE-2026-42945 in nginx. 18 years in the rewrite module, CVSS 9.2, affects \~19M instances. Found in 6 hours. 4 out of 5 findings confirmed as remote memory corruption.
18 years of human review missed it. Thousands of contributors. Fuzzing. Static analysis. All missed it. The bug was a logic issue in the two phase processing that only showed up under specific concurrent conditions.
Makes me wonder what else is hiding in our infra repos. We run tfsec and checkov on everything and they catch the obvious stuff. But they missed a terraform module where a security group allowed 10.0.0.0/8 ingress on a port that only needed access from a single /24. Technically valid, but way broader than necessary. Started using verdent for review on our terraform modules and it flagged that immediately. Both scanners and two human reviewers had approved it because the rule wasnt technically "open". Embarrassing.
If 18 years of nginx review can miss a CVSS 9.2, our infra code is probably full of similar blindspots.
https://redd.it/1tf08o8
@r_devops
Notes on monitoring Claude Code in production: OTel temporality, cost-as-estimate, cost attribution by team
Hi! Just a little post about getting visibility into Claude Code usage when an org rolls it out across teams (or for your unhinged self, obviously). So Claude Code emits OpenTelemetry metrics now (yay!) That landed quietly in the docs and the community who are busy vibe coding I guess but it ends up being very the practical if you have a real otel-based o11y stack. I've been running this on a Prometheus backend for a bit and wanted to share the gotchas worth knowing up front, because none of them are obvious from the spec.
https://preview.redd.it/n1ty9j2tsi1h1.png?width=1840&format=png&auto=webp&s=3c8581089be9546b68a4dcab74bd6757b5793e5c
For the dashboard side: I built one in PromQL that implements all of this, as the OSS-stack parallel to the existing Azure Application Insights dashboard (25052 by 1w2w3y on Grafana Labs). MIT licensed. Write-up of the implementation with more screenshots is on my blog.
Article: https://rockdarko.dev/posts/grafana-dashboard-for-claude-code-on-prometheus/
Dashboard: https://grafana.com/grafana/dashboards/25255-claude-code-metrics-prometheus/
Repo: https://github.com/rockdarko/claude-code-metrics-prometheus
Things that bit me or that I had to verify against the source if you care:
1. Pin OTel temporality to cumulative. The SDK's default is cumulative now, but defaults have drifted across versions. If you end up with delta on the producer and a Prometheus-flavored consumer expecting cumulative, your rate() queries return wrong numbers silently. Set OTEL_EXPORTER_OTLP_METRICS_TEMPORALITY_PREFERENCE=cumulative explicitly on the Claude Code side and stop wondering.
2. The cost number is a client-side estimate. Claude Code computes it from token counts and per-model pricing at request time. It's useful for trend visibility and per-team attribution, but it won't match Anthropic's invoice to the cent. Cache discounts, prompt caching, and pricing changes mid-window are the main drift sources.
3. PR / commit counters only increment when Claude Code itself opens the PR or commit (e.g., via gh CLI inside a session). PRs the developer opens manually afterward don't register. Worth knowing before you wire alerts around "team X opened zero PRs this week."
4. OTEL_RESOURCE_ATTRIBUTES is the lever for org-wide visibility. Setting attributes like team=, cost_center=, project= at SDK startup propagates as Prometheus labels and gives you per-team / per-project rollups out of the same metrics. The per-user data is exposed (user.id is included by default); what you do with that is your org's call.
5. Cache hit ratio is the single biggest lever on monthly cost. It is the difference between a sustainable bill and an alarming one. Worth a dedicated panel.
Hope this helps a few in here! 😄 Cheers
https://redd.it/1texfq2
@r_devops
How do i learn devops from scratch
Hi all,
I’ve been working at an MNC for about 3.5 years now. I started as a total fresher with zero real project knowledge. They initially trained me on Linux administration, then I moved over to cloud stuff, and right now, I’m stuck doing SAP Basis L1 support for a client. To be honest, out of my 3.5 years, I spent about 8 months on a some project just doing basic health checks—basically testing if buttons worked or if addresses were loading correctly to catch obvious bugs. In my current SAP Basis role, I’ll be really don't fully grasp how the whole system works, but im slowly but surely learning something new and I’m just doing enough to get by and survive in the company. But since I already have some foundational knowledge in Linux and Cloud, I’ve started preparing for DevOps. I'm looking for a complete from-scratch DevOps roadmap and some practical advice on how to switch over.
https://redd.it/1teug62
@r_devops
Certificate pins in mobile apps
So our mobile devs team, in a moment of pure confidence (and maybe a bit too much trust in the universe), decided to hardcode certificate pinning directly into the mobile app.
Everything was fine… until last night when the certificate expired (digicert, 1 year)
And just like that, boom, production starts acting up, clients start failing, and suddenly we’re in “drop everything and fix this immediately” mode. Fortunately, this product is not used by a ton of users (yet), as its somehow a secondary product of our company.
The solution was a brand new release for both iOS and Android, just to update something that, in hindsight, probably shouldn’t have required shipping an entire app.
Now I’m genuinely curious how other teams handle this properly.
Do you rotate pins dynamically somehow? Do you use backup pins? Remote config? Or is there a more sane approach where you don’t end up in a situation where a cert expiry turns into a full-blown emergency release across platforms?
Would love to hear how people avoid this kind of self-inflicted chaos.
https://redd.it/1tes2gn
@r_devops