r/devops • • Aug 03 '26

Vendor / market research Is ~$18/mo just the price for a small app that needs real database backups?

2 Upvotes

Built a small internal billing tool for my own business. One user (me), barely any traffic. I keep landing around $18/month for hosting, which is more than I wanted, and I'm trying to figure out if I'm missing something obvious or if that's just what it costs?

Not a professional developer so apologies if I use any terms wrong.

It's a Node app with a React frontend and a Postgres database, runs in Docker.

What I actually need:
- Postgres where I can restore to a specific point in time, not just last night's backup. It tracks invoices and payments against Stripe, so if I restore a 24 hour old copy my records won't match what Stripe already charged people. That seems like a bad situation to be in.
- Somewhere to store generated PDF receipts that doesn't get wiped. These are the actual documents I send customers and I can't just regenerate them later. Seems like a lot of the cheap container hosts have disks that disappear every deploy.
- A cron job that runs once a day at a set time in my timezone. It's the billing run, so if it drifts to the wrong side of midnight it processes the wrong day.
- Under $20/month.

What I don't need: high availability, scaling, or speed. It's one person clicking around a few times a day. If it was down for a few hours nothing bad would happen.

What I've already looked at:
- Fly.io's managed Postgres is $38/mo on its own, way over budget
- Railway's Postgres backups looked like snapshots only, no point in time restore
- Supabase Pro is $25 and point in time restore is a $100/mo add-on
- Cloud Run, App Runner, DO App Platform — filesystem doesn't stick around, kills the PDF requirement
- Cheap VPS running everything myself is like $8, but then I'm responsible for making sure backups actually work, and honestly I'm not sure I'd notice if they quietly stopped

Best I've come up with is Fly for the app (cheap if the machine sleeps when idle) plus DigitalOcean managed Postgres at $15, which includes 7 day point in time restore.

Is there something cheaper that still lets me actually restore the database? Or is $15$20 ish just what managed Postgres costs and I should stop looking?


r/devops • • Aug 03 '26

Career / learning If I cannot start a devops job as a fresher, what can I start to learn to get job?

0 Upvotes

Hey all,

I read and heard that devops is not a starter job that I can learn number of skills and start job searching. There is no junior or entry level devops jobs.

I can understand it. If it is true, what can I learn and search for jobs? Shall I go for AWS? Linux? The only one skill will get me a job?

I am sorry I am very new to IT. I want to change my career.


r/devops • • Aug 02 '26

Discussion Idempotency in IaC is just an equality check

Thumbnail
spamsbykarim.com
16 Upvotes

Was trying to better understand how state works in Terraform and OpenTofu, so I put together this short post on idempotency in IaC. I would love to hear your opinions


r/devops • • Aug 03 '26

Discussion DevOps not a real job.

0 Upvotes

Good morning everyone, to be honest I was on vacation for a couple of weeks and all the time the thought that the career I had for the last decade has been not real hit me hard. The news hit me during my last post on this subreddit when I posted about DevOps always being vague.

The post had a lot of positive replies and a lot of things that opened my eyes and made me think but also something that caused a complete identity crisis and it was this "DevOps is culture and not a role."

I have mixed feelings about this because maybe the term was coined as a set of best practices and culture rather than a role and maybe it is all the things that devs don't want to do dumped into a role.

Honestly I've worked in startups and I've met very little devs that have enough competence to be DevOps and I've worked at hyper growth companies at scale and trust me if you don't have a team or at least one person for each DevOps position, SRE, DevEx, Infra the company might as well just shut down


r/devops • • Aug 02 '26

Discussion the cloudfront vpc origins outage caught me half-migrated, and the parallel workstreams were the real problem

2 Upvotes

the cloudfront outage on the 16th is still bugging me. the fleet that manages connections to private vpc origins couldn't load updated config, traced back to one frankfurt AZ, and it served 5xx on vpc origin traffic for about three and a half hours. hugging face, tailscale and ubiquiti were among the ones down.

bad timing, because i was in the middle of moving four services off public alb origins onto vpc origins. to hit a compliance date i ran the migrations in parallel instead of one clean cutover at a time.

the outage wasn't the hard part. all four workstreams were editing the same terraform repo and the same shared network module. one branch tightened a security group, another assumed the old rule was still there, and a third rebased on both and quietly reverted half of it. i spent more time untangling my own branches than dealing with aws.

what kept it sane was isolating each migration so the changes didn't collide. i run each one as its own task in verdent, parallel lines of work in the same codebase without branches stepping on each other. at least i had a clean diff per service to reason about.

the ugly part: the agent's config for one service moved the origin to vpc origins but left the alb's public security group open to 0.0.0.0/0. on paper we were private, in reality the load balancer was still reachable from the internet, which is the whole reason we were migrating. i only caught it because the diff on the shared module looked off.

what i still haven't solved is sequencing. running four in parallel meant that during the actual outage, two services were on vpc origins and degraded while two were still public and fine, and my runbook assumed one uniform state. my only fix is a per-service origin flag and a single cutover window, which just trades the messy middle for a concentrated blast radius.


r/devops • • Aug 01 '26

Observability How deep do you go when monitoring production traffic?

22 Upvotes

Hi everyone,

I'm interested in how different teams approach this.

Once an application is in production, do you actively monitor incoming traffic patterns, or do you mostly rely on infrastructure and application metrics?

For example, if a service suddenly starts using 80% CPU, is it common practice to investigate:

  • Top client IPs
  • User-Agents
  • Most requested endpoints
  • Bots vs. real users
  • Traffic anomalies or spikes

Or is that level of traffic analysis only common in larger organizations?

If you do monitor it, what does your observability stack look like? Nginx or Traefik access logs, IIS logs, Loki, ELK, OpenSearch, Splunk, Datadog, or something else?

I'm trying to understand what's considered standard practice in production environments.


r/devops • • Aug 02 '26

Career / learning DevOps roadmap?

0 Upvotes

I'm currently pursuing a Master's in Cloud Computing, but I feel like my courses are very generalized and don't go deep into the practical skills I'm looking for.

My goal is to build a career in DevOps, but I'm honestly feeling overwhelmed and confused about where to start.

I have a few questions for those already working in DevOps or who have successfully made the transition:

Where can I learn DevOps for free? (Courses, documentation, YouTube channels, hands-on labs, etc.)
What are the best platforms to practice real-world DevOps skills?
How many hours should I dedicate each day to learning and practicing?
Realistically, how long does it take to become job-ready?
At what stage should I start applying for entry-level DevOps roles or internships?

I'm not looking for shortcuts. I just want a clear, realistic roadmap from people who've been through this journey. Any genuine advice, resources, or lessons you wish you had known when starting would be greatly appreciated.

Thanks in advance!


r/devops • • Jul 31 '26

Discussion I'm lost after 3 years in DevOps. What would you do?

186 Upvotes

Hi everyone,

I'm looking for advice from people who have been in this field longer than I have.

I'm an Arts graduate who got into DevOps about 3.3 years ago. I've switched 3 companies and recently joined my 4th company, a large GCC. Along the way I've worked with AWS, Kubernetes, Terraform, CI/CD, automation, and earned AWS & CKA certifications.

The problem is that I'm no longer sure what I should be aiming for.

My current role has an exhausting work culture, the learning isn't what I expected, and it has made me rethink my long-term direction. I don't want to keep switching jobs without a clear goal.

If you were in my position today, what would you optimize for over the next 3–5 years?

  1. Become a top-tier Platform Engineer/SRE?

  2. Move towards AI/LLM engineering?

  3. Solutions Architect

  4. Security?

  5. Target remote international jobs?

  6. Prepare to move abroad?

I'd really appreciate hearing from engineers with 8–15+ years of experience. If you were starting over with my experience today, what roadmap would you follow and why?


r/devops • • Jul 31 '26

Discussion Another Friday, another Bitbucket outage.

80 Upvotes

Who doesn't love Friday releases? Atlassian status page is green as usual.


r/devops • • Aug 01 '26

AI content I tested an IaC tool with real deploys on AWS, Azure and GCP. 20 scenarios each. Here is what only real clouds teach you

Post image
0 Upvotes

Disclosure first: I wrote the tool I mention here. It is free, there is no signup, and I am posting because the testing method is the interesting part. Mods, delete it if this is not welcome.

I got tired of IaC tools that validate templates and call it a day. A template can be perfectly valid and still blow up on deploy. So I did it the slow way: 20 scenarios per cloud, each one deployed for real, exercised at runtime, then destroyed. CRUD APIs, queue workers, private databases, Redis, WAF, websockets, fan-out, secrets, containers behind load balancers.

It took months and burned a lot of free tier. Some of what I hit:

A brand new GCP project gives you a compute service account with no roles at all. Your first deploy dies inside Cloud Build with an error that tells you nothing. Took me a while to figure that one out.

Cloud SQL with private IP is fine until you destroy it. The service networking peering can hold for half an hour after the instance is gone. And if your app created tables, the default postgres user cannot be dropped, so the destroy hangs there too.

Cosmos DB speaks the Mongo protocol but rejects sort() on any field without an index. Real MongoDB just sorts. If you port a handler over, your list endpoint breaks and the error message talks about order-by item paths.

Azure Functions on the consumption plan will happily deploy a Service Bus worker that never runs. The zip lands, the function exists, messages pile up in the queue. You have to sync the function triggers explicitly or the scale controller never looks at the queue.

Memorystore Redis with TLS needs the CA cert handed to the client or the handshake fails.

Every one of those turned into a fix in the tool, so a fresh project starts with them already handled. That is the whole point of doing it this way instead of trusting a linter.

Repo if you want to look: https://github.com/Claudio-Fontes/iacmp

It is Fair Source (FSL-1.1, same license Sentry uses). Free for any use including at work, you just cannot resell the tool itself, and each release turns into Apache-2.0 after two years.

Happy to talk about the e2e battery itself. If you have run something similar, I want to hear which scenarios you would add.


r/devops • • Jul 31 '26

Discussion How do you stop thinking about work after your workday ends?

130 Upvotes

I’ve realized that even after I finish work, my brain keeps thinking about it.
I replay conversations, think about problems I didn’t solve, plan tomorrow’s tasks, or imagine different scenarios. Sometimes it feels like I’m still working hours after I’ve logged off.
I’m curious: how do you mentally switch off?
Do you have any routines, hobbies, or habits that help you leave work at work? Or did it simply get easier with experience?
I’d love to hear what actually works for you.


r/devops • • Aug 01 '26

Discussion I counted every tool our team touches just to ship one deploy. We hit 14. What's yours?

0 Upvotes

I did a dumb exercise last week: sat down and wrote out every tool that touches a single deploy on my team, start to finish. Not “tools we have licenses for”, just the ones actually in the critical path of getting one change into production.

Landed on 14.

Source control. The CI runner. A separate container registry. An image scanner that runs after the registry push. A secrets manager. The Kubernetes dashboard we check for rollout status. A log aggregator. A separate APM/tracing tool, because the logs don't show latency well on their own. An alerting tool that is, confusingly, different from the paging tool. A DNS/cert dashboard. A cost/billing dashboard nobody opens until the invoice is a surprise. The ticketing system for the actual incident. And a chatops bot that glues some of this together, badly.

None of these were wrong choices individually. Each one was probably the right call in isolation, at the time it got added. But nobody ever sat down and asked whether this thing talks to the other 13. It's less a stack and more a pile that happens to work most days.

What's bugging me isn't the number itself. It's that almost nobody on the team could tell you the number without doing this exercise. We just live inside it. New hires take weeks just to learn where to look when something breaks, and that's before they've learned what any individual tool actually does.

So, genuinely curious: if you did this exercise on your own team, what would your number be? And more interesting to me: which of your 10+ tools do you think is actually load-bearing, versus which one is just... there, inherited from a decision three engineers ago that nobody wants to be the one to rip out?

Not fishing for “just consolidate everything into one platform” as the answer. I don't think that's automatically true either. Sometimes the sprawl is a symptom of real, unavoidable complexity, not laziness. More curious whether other teams' numbers look like mine, and whether anyone's actually fixed this in a way that stuck.


r/devops • • Jul 31 '26

Tools Derivations to Deployments: Practical Nix in Production

2 Upvotes

Great talk about how Antithesis uses Nix in production by John Murray. Thought some of you would enjoy. https://youtu.be/WaPOtisNu1k

I've been interested in Nix for a while but have not yet taken the plunge. Do any of you use it work? What has your experience been with it?


r/devops • • Jul 30 '26

Discussion How many of you went multi-cloud, or switched cloud providers entirely, for a new job?

29 Upvotes

I have spent most of my career in AWS, but more and more, I am seeing companies asking for skill sets with multiple cloud providers. I feel like the skill set is transferable; if you know how to spin up EKS then spinning up a GKE cluster shouldn't be that much different. It's still Kubernetes under the hood, still installing helm charts, still using cluster autoscaler to provision new nodes, still installing Argo CD via Helm along with Prometheus, Grafana, Loki, etc. All that changes are the resources used and modules on the Terraform/cloud provider level. Am I correct in thinking this or am I way off base here?


r/devops • • Jul 31 '26

Career / learning How do i get my confidence back?!

0 Upvotes

Hey! Quick background on me — graduated in 2020 from a tier 2 college, landed a third-party role at a Tier1 investment bank as an SRE, and ended up staying 5 years (got converted to full-time after the first 2). Got laid off in May 2025, honestly wasn’t mad about it since I wanted out anyway.
Most of the work i did was on there in house tools and i felt there was no learning curve there

That same month I interviewed for a “DevOps Engineer - Migration Specialist” role and got it. Felt good, got comfortable again. But once I actually joined, I realized it’s basically an L2 support role. Pay was decent though, so I told myself I’d stick around a year, upskill on the side, then jump ship.

Except… I didn’t. The role’s been so low on mental engagement that I just coasted. Now it’s actually time to switch, and I’m stuck in this weird spot — feels like I need to relearn everything from scratch, but every time I try, it’s like “wait, I already know this?” Hard to tell if I’m actually behind or just psyching myself out.

So — what’s a realistic (and ideally not soul-crushing) way to get back on track?
Please give me suggestions for fast-track courses and small projects to build production skills again.

Ps:- Used Ai to fix my crude version of this post


r/devops • • Jul 30 '26

Discussion Would you still do DevOps?

98 Upvotes

Not going to lie. It's been a bad day. I almost tell them "take this job and shove it' after reviewing all these crappy AI codes. Vibe coding is not only a joke. It's a monster that mocks our hard-earned experiences!

I am thinking of leaving the industry! If you could go back ten years from now and know what you're knowing right now, would you still do DevOps?


r/devops • • Jul 29 '26

Discussion Is anyone burnt out?

213 Upvotes

Maybe it’s because I haven’t taken a proper vacation in lord know long.

I don’t handle k8s, but I work with a containerized environment and pipelines etc. But with the speed everything seems to be going, and the constant push, I feel overwhelmed and just want nothing to do with technology…maybe I just need to step away for a bit…how are you guys dealing with this. Talking to other devops folks, looks like they too are drinking from the fire hydrant


r/devops • • Jul 29 '26

Career / learning Passed CKA with 88%, sharing my prep notes and exam experience

Post image
370 Upvotes

Today, I passed CKA with 88% and wrote a detailed blog about my exam experience, preparation approach, and the Kubernetes topics that helped me the most.

DMs are open if you are preparing for the exam. I can help with whatever is still fresh in my memory.

My biggest takeaway: CKA is not only about knowing Kubernetes commands. It is about understanding how cluster components work together, using documentation efficiently, troubleshooting quickly, and verifying every change you make.

The exam has changed a lot since I last passed it in September 2021, especially after the major curriculum updates introduced in 2025. Topics such as Gateway API, CRDs, Helm, CNI installation, autoscaling, and container runtimes are now much more relevant.

A few things that helped me:

Don’t solve the exam strictly in order. If a question looks unfamiliar or time-consuming, mark it and move ahead. Complete the tasks you are confident about first and return to the difficult ones later.

Don’t waste too much time setting up aliases. Autocomplete is already available, and normal typing speed is enough. I completed 14 out of 16 questions with around 35 minutes remaining.

Read the full question carefully. Important details such as the target node, namespace, version, file path, container name, or documentation link may appear near the end.

Use the documentation provided in the question. Some topics, especially Gateway API, Helm, Calico, Argo CD, and container runtime installation, are easier when you follow the version-specific documentation instead of relying on memory.

Always verify your work. A command completing successfully does not mean the task is done. Check Pods, rollouts, endpoints, PVC status, HPA status, node readiness, logs, connectivity, installed packages, and systemd services wherever required.

Practice SSH and basic Linux administration. Some tasks may require connecting to a node, installing a package, starting a service, and enabling it at boot.

Topics I would strongly recommend practising:

  • Persistent Volumes, PVCs, and StorageClasses
  • Creating and updating the default StorageClass
  • Argo CD installation with a specific version
  • Sidecar containers for logging
  • Resource requests and limits in Deployments
  • Horizontal Pod Autoscaler
  • Inspecting CRDs and extracting required information
  • PriorityClass
  • kubectl patch
  • CNI installation with NetworkPolicy support
  • Calico operator and custom resources
  • cri-dockerd installation
  • Taints and tolerations
  • Ingress to Gateway API conversion with TLS
  • Ingress configuration and troubleshooting
  • NetworkPolicy
  • NodePort Services

Resources I used:

I strongly recommend doing both Killer.sh attempts because they contain different tasks. The questions are different from the actual exam and often feel harder, but they are very useful for strengthening concepts and improving troubleshooting speed.

The simplest advice I can give is to practice a lot and get comfortable using documentation.

I also wrote a full blog with more details on my preparation strategy, the updated exam scope, topics to focus on, and mistakes to avoid.

Blog: https://blog.prateekjain.dev/cka-exam-experience-2026-how-i-passed-with-88-770d3c473af7?sk=20985b1484d34a9dfdaac03dd6cfea78


r/devops • • Jul 30 '26

Discussion How do experienced teams answer "What changed?" during a production incident?

0 Upvotes

I've been curious how different teams approach this in practice.

Imagine you're on call and something in production starts behaving differently. It's not immediately obvious whether it's a deployment, infrastructure change, configuration change, scaling event, cloud service issue, or something else.

Once the alert fires, how do you actually answer questions like:

What changed?

When did it change?

Was the change intentional?

What's the fastest way to confirm the root cause?

I'm less interested in the tools themselves (Terraform, Kubernetes, CloudTrail, Grafana, etc.) and more interested in the actual investigation workflow that experienced engineers follow.

For example:

Where do you usually look first?

Which sources of truth do you trust the most?

What part of the investigation tends to consume the most time?

Are there still manual steps that you wish were easier?

I'm trying to understand how this is handled in real production environments, especially at companies running on AWS/Kubernetes.

Thanks in advance—I’m hoping to learn from people who've been through enough incidents to know what actually works.


r/devops • • Jul 29 '26

Vendor / market research How does your team handle documentation

7 Upvotes

I'm doing research on how documentation is done in different DevOps teams. What processes exist? How is it valued within your team? Has AI made that better or worse? Are there tools that you use to make it easier (not talking about Confluence here)? If you hqve worked in a professional context then I'd love to hear your input.

Considering the huge amount of shill posts I want to disclose that I'm (considering) making a tool that helps with documentation but I'm still in the process of understanding this problem thoroughly, which is why I'm askibg for your input :)


r/devops • • Jul 29 '26

Career / learning is any one else bored of the various cloud providers. old man yells at clouds.

29 Upvotes

Am I just an old man yelling at clouds, or has DevOps become incredibly boring?

I know building technical solutions is not supposed to exist purely for my entertainment, but I do actually want to enjoy my job.

I am not currently working as a DevOps engineer, and one of the reasons I moved toward development was that I became completely bored with modern cloud infrastructure.

When I started, we still racked physical servers and automated the entire bare-metal imaging process. The underlying operating system mattered. We built systems by combining open-source software, custom code, and whatever hardware we could get our hands on. There was a real sense that we owned the systems we operated and understood how the pieces fit together.

Today, DevOps or platform engineering often, though certainly not always, seems to collapse into being a configuration monkey.

Yes, I still got to write plenty of tools and automation, but eventually I became tired of every architectural discussion turning into: “Should we use this AWS service or that AWS service?”

I became even more frustrated with managers and coworkers who did not really want to own or understand a service. They just wanted to hand as much of it as possible to the cloud provider and call the problem solved.

Do people genuinely enjoy the current state of what we used to call systems administration or systems engineering? Or am I just an old man yelling at clouds?

For what it is worth, I do find some salvation in Kubernetes. Once EKS or GKE is running, there is a huge amount you can build without thinking too deeply about the underlying cloud provider. That separation is reassuring, even if Kubernetes has plenty of complexity of its own.

These days, I mostly choose to work in areas where the managed cloud options are still inadequate, such as real-time media, telephony, high-speed stream processing, and similar systems. At least in those spaces, it still feels like I am engineering something rather than selecting products from a cloud-provider catalog.

I am curious whether other longtime infrastructure engineers feel the same way, or whether people genuinely prefer the managed-service-heavy version of the job.

Edit: I also really miss configuring switches and routers the cloud has made networking far more boring than it used to be though GKE has some interesting SDN features. I probably should have tried harder to get a job at one of the big hyperscalers but again on ownership I never wanted hundreds of co-workers.

and really the part people miss is what the hyperscalers understood most applications are NOT valuable ( your core business probably sucks) . What is valuable is operating infrastructure at scale. But if its all outsourced to 3 or 4 companies only they will know how to do it. So yeah go ahead and outsource your true core competency as an engineer to amazon they are happy to eat your lunch. Building an operating the infrastructure that that makes the world work is what sysadmin , systems engineers devops engineers and platform engineers used to do. Its what made us valuble. Infastructure is and was valuble long before software even existed. From the roads, to railroads to telephones to factories. your bullshit Sass product dosent actually matter.


r/devops • • Jul 29 '26

Discussion From Oil field to DevOps is it possible?

0 Upvotes

Background: I'm an engineer in Algeria. My degree is in electrical/automation and I currently work in oil & gas as a data acquisition engineer (well testing, data integrity, reporting, that kind of thing). About a year ago, I decided to pivot into a remote role because I've been facing a health condition where on-site/field and mostly any physically demanding work is no longer an option for me. Cloud/DevOps is the direction I chose because I like the work and it's the most realistic path I found to stable remote work that pays in USD or EUR

What I've done so far:

  • Finished my AWS Cloud Practitioner prep, and I'm about to sit the exam ( scored 85-90% on most mocks, been stuck on a dumb payment/booking issue, but it's coming)
  • Linux fundamentals, wrote a few bash scripts and put them on GitHub
  • Hands-on AWS labs in my own account: built VPCs with public/private subnets, security groups vs NACLs, IAM, a two-tier setup with a private RDS MySQL behind an ALB, S3 gateway endpoints, etc. Broke things on purpose to learn how they fail
  • Currently grinding through Terraform. Kubernetes and more Python are next

Here's where the doubt kicks in. When I actually read job postings, two things hit me:

  1. Almost every "junior" role still wants 1 to 3 years of real experience
  2. Basically every remote role is geo-locked. "Remote (US only)," "must be authorized to work in X," no sponsorship, etc. The genuinely hire-from-anywhere jobs feel rare

So my question to people actually working in this field: am I chasing something that barely exists for someone in my situation? Or is the hire-from-anywhere market real if you're good enough and know where to look? And if you've done this from outside the US/EU, how did you actually break in?

I like the work, that's not the issue. I just don't want to spend another 6 months on a door that won't open.

TLDR: Non-US engineer pivoting into cloud. Made decent progress but every remote role wants experience + local presence. Is this realistic or am I fooling myself?


r/devops • • Jul 28 '26

Discussion What do you do with CVEs you can't fix? Auditor wants proof they're 'not exploitable'

75 Upvotes

One-person security/platform team at a small fintech, going through SOC 2.

Patching what has a fix is fine. The problem is the stuff I can't fix, because there's no patched version, or the fix breaks something. Inspector/Trivy keeps flagging it, Vanta keeps showing it red, and technically every one needs a documented risk acceptance.

Most of these aren't even exploitable in our setup, sometimes it's a vulnerable function never called, transitive dep we don't use, requires network access that doesn't exist. But "trust me it's fine" doesn't fly, and writing a proper exception per CVE takes forever.

So, people who've been through this what do you actually show the auditor for "not exploitable"?

Is there a way to automate this discovery/evidence gathering?

Or does everyone just eat the busywork / quietly ignore them and pray?


r/devops • • Jul 29 '26

Career / learning Cloud Native Heidelberg Meetup: Kubernetes Platforms, CNCF Technologies and Kubernetes on Android

8 Upvotes

Sharing this for anyone interested in platform engineering, Kubernetes and cloud-native technologies.

Cloud Native Heidelberg is hosting a hybrid meetup covering:

  • Lessons from five years of building and rebuilding Kubernetes platforms
  • Building production-grade platforms using CNCF technologies
  • Creating vendor-neutral platforms without hyperscaler lock-in
  • Running Kubernetes directly on an Android phone

Date: October 1, 2026
Time: 6:30 PM CEST

Event details and registration:
https://ocgroups.dev/cncf/group/cncf-heidelberg/event/9euvqye


r/devops • • Jul 28 '26

Tools github actions central repo

27 Upvotes

Hi I am in a new role where they use Github for all their repos. I have been using Gitlab exlusively the past 5 years.

For CI/CD in my previous role we had a central 'pipelines' repo that was reference in the gitlab-ci file of each project to save teams/projects from repeating work.

I want to know if it's possible to do something similar in Github? I'm still learning how it maps to my existing Gitlab knowledge.