Collaboration DevOps Engineer for a Decentralized AI Compute Network (DistriAI)

Hi everyone,
I’m building DistriAI, a decentralized AI compute network that aggregates unused CPU/GPU power from everyday devices (smartphones, laptops, desktops) into a globally distributed inference layer.

We’re entering the next stage of development, and we’re looking for someone with solid DevOps / Infrastructure experience to help shape the network’s backbone.

⸻

What DistriAI is doing

We orchestrate and validate micro-tasks across thousands of heterogeneous nodes, aiming to build a censorship-resistant, cost-efficient alternative to centralized compute providers.

Think DePIN × AI orchestration, with an emphasis on performance, security, and reliability.

⸻

What we already have:
• architecture v1 + v1.1 updates
(segmented node pipeline, scheduler, circuit breakers, adaptive rate limiting, RBAC, early fraud detection, reward-meter stub, audit logging…)
• whitepaper
• technical roadmap
• tokenomics
• presale structure
• backend + smart contract contributors
• security engineering support
• early monitoring + observability baseline

The core foundation is ready — now we want to harden and scale the infrastructure layer.

⸻

What we need from DevOps

A DevOps engineer who can collaborate on:

Infrastructure & Scaling
• containerized microservices
• orchestration (Kubernetes preferred)
• distributed task execution pipelines
• autoscaling & workload distribution

Observability
• metrics, logs, distributed tracing
• node heartbeat & uptime tracking
• anomaly + fraudulent behavior detection

Security & Reliability
• secure CI/CD
• secrets management
• vulnerability scanning
• fault-tolerant compute routing

Tooling
• local + cloud deployment tooling
• zero-downtime upgrades
• environment config management
• developer experience pipelines

⸻

Tech (flexible)

Docker, Kubernetes, NATS/Redis/Kafka, Prometheus/Grafana, Loki/ELK, Terraform, GitHub Actions.

Not required to know everything — but you must be comfortable designing systems that scale and survive.

⸻

Who we’re looking for
• someone who likes building infra from scratch
• strong reliability mindset
• experience with distributed systems or high-load environments
• ownership + clarity in communication
• ability to collaborate with backend/security contributors

⸻

If interested

Drop your GitHub, LinkedIn, or previous infra setups, or DM me directly for more details.
Happy to walk you through the architecture and where you’d plug in.

Let’s build the backbone of DistriAI together.

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

Are there any good reasons anymore to use a Virtual Machine (leaving alone emulation needs for cross-compiling) over Docker or devcontainers when developing an application? I keep hearing that at this point there is no reason as even container security can be hardened.

Are there any good reasons anymore to use a Virtual Machine (leaving alone emulation needs for cross-compiling) over Docker or devcontainers when developing an application? I keep hearing that at this point there is no reason as even container security can be hardened.

Thanks so much and I’m sorry if this is a boring noob question.

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

Do you guys actually use AI to code or am i just overthinking this?



I think I'm starting to realize how normal it’s becoming to lean on AI for coding. Tools like Cursor, Windsurf, Continue, all that, are just part of the workflow now. even our prof was cool with it as long as we can explain what the code is actually doing.

I tried Cursor for the first time and honestly it was nice. something that would’ve taken me hours turned into writing a few prompts and fixing tiny mistakes. But it feels like i’m skipping the “learning” part.

I've been mixing in other stuff too Aider, GPT Pilot, even Cosine here and there just so i don’t lose track of how files connect when a project gets messy.

I think i’m just trying to figure out the balance. are we supposed to fully embrace these tools or use them sparingly so we actually learn? how are you all handling this?

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

Opsgenie alternatives

My team is currently using Opsgenie + Prometheus as a main way to react to important accidents. However, Opsgenie will shut down in 2027. So, please share your experience with other similar tools, preferably easy to use and open source.

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

Moved from Service Desk to DevOps and now I feel like a complete imposter. Need advice.

Hey everyone,

I really need some advice from people who’ve been in this situation.

I’ve been working in Service Desk for about 3 years, and somehow I managed to crack a DevOps interview for a FinTech startup. It felt like a huge step forward in my career.

But now reality is hitting me hard…

The team has started giving me an overview of their tech stack, and honestly, it’s stuff I’ve only heard of in videos or blogs. Things like CI/CD, AWS services, Terraform, Docker, pipelines, monitoring, etc. I understand the concepts, but I’ve never actually worked with them in a real environment.

I’ve never SSH’d into a real server, never used a real AWS Console, nothing. And now I’m feeling very small, like I’m not supposed to be here.

They think I know a lot because I interviewed well and answered most of the questions confidently. But internally I’m panicking because I don’t want to embarrass myself or let the team down.

I’m not trying to scam anyone, I genuinely want to become good at DevOps, but the gap between theory and real-world work feels massive right now.

So my question is:

How do I prepare quickly so I don’t feel like an imposter on Day 1?

What should I practice?

What projects should I build? How do I get comfortable with AWS, Linux, and pipelines before actually joining?

Any guidance from people who made the same transition would mean a lot. 🙏

TLDR: Coming from Service Desk with no real hands-on DevOps experience (no AWS, no SSH, no pipelines). Cracked a DevOps interview but now feel like an imposter because the tech stack is way beyond what I’ve practiced. Need advice on how to prepare fast and not freeze on the job.

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

Early feedback wanted: automating disaster recovery with a config-driven CLI.

I'm building a CLI tool to handle disaster recovery for my own infrastructure and would like some feedback on it.

Current approach uses a YAML config where you specify what to back up:

# backup-config.yaml
app: reddit

provider:
name: aws
region: us-east-1

auth:
profile: my-aws-profile
# OR use
role_arn: arn:aws:iam::123456789012:role/BackupRole

backup:
resources:
- type: rds
name: production-databases
discover: "tag:Environment=production"
- type: rds
name: staging-databases
discover: "tag:Environment=staging"

Right now it just creates RDS snapshots for anything matching those tags.

\*\*Would love to hear:\*\*

\- Thoughts on the config design

\- What resources you'd want supported next

\- Any "this will be a problem later" warnings

GitHub: [https://github.com/obakeng-develops/sumi](https://github.com/obakeng-develops/sumi)

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

Master's in cloud or DevOps

I want to do master's in cloud or DevOps in Australia
And find work right there after
I have barely a year of experience
Which university should I go for?
Suggestions/thoughts?

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

We open-sourced kubesdk - a fully typed, async-first Python client for Kubernetes. Feedback welcome.

Hey everyone,

[Puzl Cloud](https://puzl.cloud/) team here. Over the last months we’ve been packing our internal Python utils for Kubernetes into **kubesdk**, a modern k8s client and model generator. We open-sourced it a few days ago, and we’d love feedback from the community.

We needed something ergonomic for day-to-day production Kubernetes automation and multi-cluster workflows, so we built an SDK that provides:

* Async-first client with minimal external dependencies
* Fully typed client methods and models for all built-in Kubernetes resources
* Model generator (provide your k8s API - get Python dataclasses instantly)
* Unified client surface for core resources and custom resources
* High throughput for large-scale workloads with multi-cluster support built into the client



**Repo link:**

[https://github.com/puzl-cloud/kubesdk](https://github.com/puzl-cloud/kubesdk)

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

Ransomware-as-a-Service (RaaS): The Cybercrime Business Model Democratizing Attacks 💼

https://instatunnel.my/blog/ransomware-as-a-service-raas-the-cybercrime-business-model-democratizing-attacks

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

Launch container on first connection

I'm trying to imagine how I could implement Cloud Run scale to zero feature.
Let's say I'm running either containers with CRIU or KVM images, the scenario would be:
- A client start a request (the protocol might be HTTP, TCP, UDP, ...)
- The node receives the request
- If a container is ready to serve, forward the connection as normal
- If no container is available, first starts it, then forward the connection

I can imagine implementing this via a load balancer (eBPF? Custom app?), who would be in charge of terminating connections, anyhow I'm fuzzy on the details.
- Wouldn't the connection possibly timeout while the container is starting? I can ameliorate this using CRIU for fast boots
- Is there some projects already covering this?

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

Company is starting on-call soon. What should I request from management? Money? Separate phone? etc...

For reference, I'm in the US, a salaried employee, and 100% remote.

We've been working on a greenfield project for a few years that is now just going live and it's going to require our entire department (not just my team) to be on-call.

I guess this is my chance to make some requests from management. Should I ask to be compensated for on-call? Should I ask for a separate phone? Should I pull out my contract and refuse to do on-call if it's not in writing?

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

Should I give my fiver dev my login to my hosting account?

So I am asking because I don’t know if it is safe to give the developer I hired my login with my personal information on the account.

He said “The work related to Dokan requires noscripting in the backend inside the custom files. This cannot be done from the WordPress dashboard. And for noscripting, the database also needs to be configured so without access to the database, how will the work be done?
And if I’m editing but I don’t have hosting permissions, then how will I insert the noscript?”

So I made him a database dev account on phpmyadmin, a cPanel ftp account, and an admin account on my Wordpress site for him but he said that he still needs my login. Is it safe/should I give him my login? He has 5 stars and 178 reviews on fiver and from Bangladesh.

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

From PSI to kill signal: logic I used so auto-remediation doesn’t kill good workloads

Last week I posted here about using Linux PSI instead of just CPU% for “is this box in trouble?” checks.

This is a follow-up: if you trust PSI as a signal, how do you actually act on it without killing normal spikes?

The naive thing I’ve seen (and done myself before) is:

if CPU > 90% for N seconds -> kill / restart

That works until it doesn’t. Enough times I’ve seen:

JVM starting
image builds
some heavy batch job CPU goes high for a bit, everything is actually fine, but the “helper” noscript freaks out and kills it. So now I use 2 signals plus a grace period.

Rough rule:

1. CPU is high (example: > 90%)
2. AND CPU PSI is high (example: cpu some avg10 > 40)
3. AND both stay high for N seconds (I use 15s) If any of these drops during the grace period, I reset state and do nothing.

Only if all three stay true for 15 seconds, then I:

look at per-process stats (CPU, fork rate, short jobs / crash loops)
pick the top offender
send kill to that one process

This avoids the classic “kill → restart → kill → restart” loop from pure CPU-based rules. Short normal spikes don’t keep PSI high for 15 seconds. Real runaway jobs usually do.

I wrote up the Rust code that does this:

read /proc/pressure/cpu (PSI)
combine with eBPF events (fork/exec/exit)
apply the rule above and choose a victim

Write-up + code is here: [https://getlinnix.substack.com/p/from-psi-to-kill-signal-the-rust](https://getlinnix.substack.com/p/from-psi-to-kill-signal-the-rust)

This runs inside Linnix (small eBPF-based tool I’m hacking on: [github.com/linnix-os/linnix](https://github.com/linnix-os/linnix)), but the idea is generic. Even a bash noscript checking /proc/pressure/cpu in a loop with a grace period would be safer than plain CPU > 90% -> kill.

Curious how people here handle this:

Do you use a grace period for auto-remediation (k8s, systemd, custom noscripts)?
Do you gate actions on more than one signal (CPU + PSI / latency / queue depth / error rate)?
Any stories where “CPU threshold → restart/kill” caused more damage than it fixed?

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

Beginner in AWS: Need Mock Tests and Project Recommendations

I’ve been learning AWS for the past 2-3 months, along with Terraform, Gitlab, Kubernetes, and Docker through YouTube tutorials and hands-on practice. I’m now looking to work on more structured, real-world projects - possibly even contributing to public cloud related projects to build practical experience.

I’m also planning to take the AWS Cloud Practitioner exam. Could anyone suggest resources or websites that offer mock tests in an exam-like environment? Also, any recommendations for platforms where I can find beginner-friendly cloud projects to build my portfolio would be greatly appreciated.

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

Any good DevOps podcasts?

Joining a company operating in the DevOps space and I want to keep up to date with current trends.

Any good podcasts you recommend?

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

RSS Feeds - DevOps, Cloud, etc

Hey everyone!

Kind of a fun post here but wanted to refresh my Reeder app and do some spring cleaning. With the advent of so much this year between AI and all sorts of barely-working-great-ideas from Harvard MBAs, thought it would be nice to see what kinds of RSS feeds people use/watch regularly across a few topics:

* DevOps
* Cloud (AWS, Azure, GCP, whatever)
* Infrastructure tech like CDNs, WAFs, ALBs, etc
* Platform Eng like K8s, docker, etv.
* Programming, maybe fixated on IaC as a topic

Anyway, my feeds have been a mix of broken or just not great lately and though I'd ask the community.

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

Backstage plugin to update an entity

i have created a backstage plugin to allow updating a catalog entity from the same scaffolder template it was created with, this allows updating an entity as a self service from the same entity page, the values are pre populated, with conditional steps if needed.


you can check it out here
Entity scaffolder plugin

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

Azure Engineer or SRE more future?

I am a fresh grad with 1 year working experience (including internship) as a backend developer. I am really interested in cloud and DevOps. I recently received 2 interviews: Azure Engineer and SRE. I wonder which path has more future ?

The Azure Engineer position basically focus on IaaS , deployment, write Teraform. They said might have chance to do cicd pipeline in future... I am wondering is it a good path to go for Cloud engineer/ DevOps engineer? Because they also mentioned that it is bery easy to pick up... I am afraid if this is just a simple deployment job. But they do mentioned that I will do the design infrastructure etc. and a lot of things to learn.

Or SRE better? Which path has more future?
Hope to seek opinions from you all ..🙏🏻

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

List of 50 top companies in 2025 that hire DevOps engineers!

https://devopsprojectshq.com/role/top-devops-companies-2025/

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

Is Continuous Exposure Management the true SecDevOps endgame?

We talk a lot about "Shift Left," but the reality is security findings often hit the CI/CD pipeline late, or they are generated by a vulnerability scanner that doesn't understand the context of the running application.

I'm looking at this idea of Exposure Management, which seems like the natural evolution of SecDevOps/SRE practices. It forces security to be integrated and continuous, covering the entire lifecycle: code repos, cloud configurations, deployed application, and user identity. The goal is to continuously assess risk, not just find flaws.

If you are running a mature SecDevOps pipeline, how are you ensuring that security findings from different tools (SAST, DAST, CSPM, etc.) are unified and prioritized to show a single, clear measure of risk, rather than just raw vulnerability counts?

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

Devops tool builder

Hi. I am 7+ year devops experience have been building some SaaS products for a while. I want to contribute for devops community. Is there any tool that would help devops. I thought about incident management, auto resolution but some companies have been doing them. And AWS also announced AWS Devops Agent today. Is there any part of the daily worklife of devops, sre and sys admin thats often overlooked by the devops tool companies with or without AI.

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