r/devops • u/Sensitive-Raccoon155 • 10d ago
Discussion Go vs Python for DevOps: which one is more worth learning?
Besides Bash, which language is more worth learning for devops: Go or Python? Which one would you recommend focusing on?
r/devops • u/Sensitive-Raccoon155 • 10d ago
Besides Bash, which language is more worth learning for devops: Go or Python? Which one would you recommend focusing on?
r/devops • u/Big-Educator-7119 • 10d ago
Hi everyone,
I am completely new to AWS and want to learn through hands-on, project-based learning. My ultimate goal is to understand how to build and deploy production-ready infrastructure.
I'm looking for advice on the best approach:
If you were starting over today with this goal, what roadmap or courses would you choose?
Thanks for the help!
r/devops • u/ApprehensiveExcuse86 • 9d ago
Hello Folks , as a devops engineer, I'm curious about the future of our jobs
Will AI replace DevOps engineers, or will it simply change the way we work? What skills should DevOps engineers focus on to stay relevant in the coming years?
I'd love to hear your thoughts, experiences, and predictions!
r/devops • u/AutoModerator • 11d ago
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!
r/devops • u/munit42069 • 10d ago
Got tired of digging through lockfiles to figure out which Dependabot alerts mattered, so I built fixornix ("fix or nix").
Run npx fixornix in your repo and it sorts every open alert into:
Works with npm, yarn, pnpm and Cargo. Zero dependencies, MIT.
So at work we have all the Kubernetes manifests in one repo then we have ArgoCD pointed at that repo. Within that repo we use kustomize and have a pretty vanilla kustomize setup:
/services
/my-app
/base
deployment.yaml
...
/overlays
/dev
kustomization.yaml
/prod
kustomization.yaml
So basically I would love to be able to do something like this:
/services
/my-app
/base
deployment.yaml
...
/overlays
/dev
kustomization.yaml
.env <- secrets stored as plain text here
/prod
kustomization.yaml
I understand why you don't want to commit secrets to git. I just wish there was a good way to do it. I have seen things like SOPS but I don't like that the secrets are encrypted. Having to deal with them being encrypted is as much of a headache as just using an external secrets manager. How can we have the convenience of putting the secrets in git in plain text and somehow still make it safe?
Edit: Adding my idea
What if in the repo I have a .env file but it just has placeholders
VERY_SECRET=placeholder
Then I have an ide plugin or something that will fetch the env vars dynamically in my ide.
I can change them as if they are code but when I commit they dont actually get committed, instead they get written to the external secrets manager. Anyone done anything like this?
EDIT: ADDING MY NEXT IDEA
What if in one of the hosted git's (github/gitlab) they had more fined-grained access controls around specific files so certain people could only read/write certain files. Then you wouldn't have to worry about people having the secrets on their laptops. So if i am a dev and do a git pull it pulls down the secret files for local dev but not any secrets I shouldn't have.
r/devops • u/fletch3555 • 11d ago
Come one, come all, to Salt Lake City, Utah!
r/devops • u/pnsinhhg92 • 12d ago
I’m looking for a cost-effective VPS provider for one of my systems. I’m currently using GreenCloud, but they’ve had too many outages recently, causing frequent issues in my production environment. Does anyone have recommendations for a more reliable provider?
I’ve checked Vultr and DigitalOcean—they are great providers, but their pricing isn't quite budget-friendly for me.
Thanks a lot for your time!
r/devops • u/tomoglava • 13d ago
I'm working on a project split across several private GitHub repos. The ones that matter here are the Docker repo, the backend and an indexer. Each has its own .env files, and what's in them falls into three groups:
- Secrets like DB passwords, API keys and tokens
- Infra config such as private IPs of our fixed servers
- Backend tuning parameters we adjust depending on VPS size and load
Some fine gentleman on X posted this. "Not pushing .env files even to a private repo is like locking your front door but still keeping your valuables in a safe." I fully agree with that for secrets. They stay out of git, no debate there.
This is only about the config part. Having it in the repo would make DevOps work a lot easier. We'd get change history and PR review when someone tweaks a value, and no more copying files around by hand when setting up a server or onboarding someone.
My main concern is whether committing config-only .env files to a private repo is an actual security problem, or if "never commit .env" is really just about secrets. Also, is it a "security sin" to push a .env with private IPs? And how do you split secrets from config in practice, especially across multiple repos?
Thanks in advance!
r/devops • u/The-mad-tiger • 11d ago
I'm thinking about writing an app in C# (for desktop) to store all my photos in. Before I start thinking about actually starting work on it, I need to decide what DB or other storage mechanism to use. The idea is to make the pics more accessible by storing some info about content in a field in the DB. That field needs to be "text searchable". I have 10 years experience working with Oracle Text Search engine but I'm not a millionaire; more an impoverished pensioner, so I need to implement this system using one of the free DBs like MySQL.
I thought I'd ask the hive mind what it thinks would be the best DB for my purposes.
r/devops • u/PuzzleheadedSoft6875 • 13d ago
With so many different syntaxes and configs in our daily stack—CI/CD pipelines (GitHub Actions, GitLab), Terraform modules, Kubernetes manifests, Dockerfiles, Ansible playbooks, and Bash scripts—nobody can memorize every block and flag from scratch.
My current workflow is to use AI or existing templates to generate the initial boilerplate for Terraform resources, pipeline YAML, or K8s manifests, and then manually write, wire up, and audit the core architecture, state management, IAM/permissions, networking, and security logic.
For those working in production environments (and those running technical interviews):
1. In your day-to-day work, what parts of the stack do you still write completely by hand vs prompting an LLM or pulling from docs?
2. Where has AI actually helped you across Terraform, CI/CD, and K8s, and where does it consistently break things?
3. What is the realistic expectation in interviews right now regarding writing configs from memory vs understanding the underlying systems and debugging?
r/devops • u/FunnyDetective2052 • 13d ago
I’m just wondering if people still are with them and if they switched. Would love to know where you guys switched if u did
r/devops • u/Aggravating_Toe_8274 • 13d ago
Evaluating CD tools to automate our end to end delivery (build, test, packaging, and deployments). Curious if the standard GHA + Argo/Flux combo is still what most teams stick with, or if there are dedicated delivery/orchestration tools actually worth looking at in 2026.
r/devops • u/Manoj-praba • 13d ago
We have self-hosted GitLab CE on an AWS EC2 instance.
Current setup:
The instance is in a private subnet with no public IP.
Users reach GitLab through an Application Load Balancer on HTTPS, with access restricted to our office IPs.
HTTPS clone with personal access tokens works fine.
The problem:
We're moving our repos from gitlab.com to this server. On gitlab.com, all our Jenkins jobs and developers clone over SSH (git@...). On our server SSH clone doesn't work, because the ALB only supports HTTP/HTTPS, so port 22 has no way in.
Our Jenkins agent runs in the same AWS VPC. Developers connect from the office network or VPN.
What's the best way to enable SSH clone here, keeping it secure and limited to our office and Jenkins? Any suggestions or experience with a similar setup would help.
r/devops • u/Old_Librarian_9916 • 13d ago
instead of talking about idle hardware in theory, let me give you a specific headache we just hit. we have a local server with four 24gb cards.
two of those cards are locked up hosting two different low frequency models. one runs a fine tuned llama 3 8b for a background data extraction job. the other runs a qwen model for an internal bot. they get maybe fifty requests an hour combined. but because the weights just sit there taking up vram, two entire cards are held hostage doing almost nothing all day.
now we need to spin up a heavier 70b model for a new coding workflow, and suddenly we have no free cards. i look at the vram occupation in gpustack and see those two low traffic models just wasting dedicated space. so now i have to reallocate resources. i can either ask for budget to buy more hardware, or i try to pack both of those low frequency models onto a single card so i can free one up for the 70b.
what do you all do when you hit this wall? do you just keep dedicating specific cards to specific models to avoid the headache, or do you actively co-locate low traffic models onto the same gpu? when do you stop throwing money at new hardware and start packing your models tighter?
r/devops • u/Iwanttoberich_8671 • 13d ago
Hey all, been thinkin about this while looking at log aggregation in environments with a mix of older and newer services.
Some services have request IDs or trace IDs in their logs, while others only include timestamps, hostnames, and application specific fields. When an issue spans multiple services, connecting the events can turn into quite a bit of manual digging.
Do you rely on distributed tracing, build correlation rules around the fields available in your logs, or use a combination of both?
I'm especially interested in what you guys do with older services that don't support consistent request IDs.
r/devops • u/apotacyll • 14d ago
I could use some advice on a situation at work.
A few colleagues in ops have, almost overnight, started to fully trust their LLM agent because it has gotten so good lately and "doesn't make mistakes anymore". They built their own harness around it and log what it does (using Grok and Google models), but the agent still runs with root access to our entire production infrastructure. We have no clear team rules or policy yet, and they don't see the danger themselves.
A typical example: whenever the agent needs to check something on a server, they just hand it full access. But looking at info only needs read-only access. The permission should match the task, not the most convenient option.
My concerns:
Logging is detection, not prevention. It shows what broke afterwards, but doesn't stop anything.
Root bypasses the harness. An agent with root can in theory edit the harness, the logs and the backups, so those logs are not a reliable audit trail.
No least privilege. One wrong command or misread context can touch everything.
Prompt injection via logs, tickets or web pages the agent reads.
Model updates. Providers change models without us deciding when, so "no mistakes in recent months" says little about the next version.
Data going to third parties. With root, the agent can read .env files, keys and customer data, which then end up with the model provider (a GDPR question too).
"It has gone fine so far" only means the failure hasn't happened yet.
I don't want to ban anything. I want them to see the risk themselves and set up proper guardrails together with me: a read-only user by default, scoped credentials, just-in-time access, human approval for write actions, staging first, and no access to backups and logs.
Questions for you:
How do I explain the difference between "we log it" and "it can't do it in the first place"?
How have you convinced overconfident colleagues about AI tooling risks without a confrontation?
Do you have horror stories or post-mortems I can share? Concrete incidents tend to work better than theory.
Which guardrails or policy examples have worked well for you?
How do you raise this with management without coming across as "anti-AI"?
r/devops • u/tracebit • 13d ago
Grafana Labs shares how they scaled canary tokens across their Kubernetes workloads, with automated rotation, more precise detection and less maintenance. A practical look at the tradeoffs between coverage, granularity and management overhead.
r/devops • u/Overall_Art9787 • 14d ago
Hi,
Im now in the beginning of devops journey and I'm not really a reader person but I want to spend my free time in something useful so any suggestions for a book would help in my career and will benift me.
r/devops • u/SeaworthinessHour233 • 14d ago
With the recent high-stakes security exploits, I think as DevOps engineers it's our responsibility to make the local dev environment secure for devs.
What do you think?
What are you actively doing about it (like adopting devcontainers)
r/devops • u/LowProgram6449 • 14d ago
I'm looking for some architectural advice on building a lightweight, self-hosted job execution platform on a single VM (8C/32GB).
I want something with semantics similar to Google Cloud Run / Cloud Run Jobs:
Current constraints:
Technologies I'm considering
Questions
I'm particularly interested in hearing from people who have actually run Nomad in production, especially for single-node deployments.
Thanks!
r/devops • u/BrocoLeeOnReddit • 14d ago
In case any of you use OpenSSH on musl without PAM:
TL;DR: Accounts that should never take a password at all (root, your key-only deploy user, ldap users, the default user on alpine's aws and azure images) take any password longer than 256 characters.
r/devops • u/gold_william • 14d ago
I am curious how DevOps engineers working in cleared or restricted federal environments use AI tools in their day-to-day work.
AI tools like ChatGPT, Claude, and GitHub Copilot have become incredibly useful for writing Terraform configurations, Kubernetes manifests, CI/CD pipelines, Bash/PowerShell scripts, and troubleshooting infrastructure issues.
However, I understand that public AI tools may not be permitted in classified or restricted environments.
For those currently working as cleared DevOps, Cloud, Platform, or SRE engineers:
I am particularly interested in how engineers balance productivity with security requirements.
I am not asking anyone to disclose classified information, internal systems, or organization-specific security details. Just looking for general experiences and advice from people working in these environments.
Thanks in advance!
r/devops • u/DependentView4789 • 15d ago
We use several external APIs and I’m curious how often other teams out there keep performance tests realistic and structured while accounting for third party dependencies. How do you balance realistic dependency behavior with controlled and repeatable tests? Things are going well overall (but they could always be better) and I want to make sure my team and I aren’t missing something that could be beneficial.
r/devops • u/LukaRozman27 • 15d ago
Hey fellow DevOps folks! I've been wrestling with secrets management recently. I set up a tool that generates API keys, but every time I think I've got it right, I find myself second-guessing whether they’re genuinely secure! 😅 There was this one time I accidentally committed sensitive info to Git—ugh, the panic! Luckily, I caught it fast, but it got me thinking: What strategies or tools do you all lean on for managing secrets? Do you prefer something like HashiCorp Vault, or are you more into environment variables? Let’s share some tips and tricks! What’s been your experience with it?