r/DevOpsLinks • • Nov 16 '25

Monitoring and observability How do your teams maintain long-term code visibility beyond CI/CD checks?

7 Upvotes

I’ve been researching how different teams approach ongoing visibility into code health, maintainability, and long-term risk, especially when delivery cycles move fast. CI/CD usually handles tests, deployment checks, and security scanners, but I’m curious about what happens beyond that the part that affects future refactoring effort, engineering cost, and architectural sustainability. A few open questions I’d love thoughts on:

  1. Do you track code health or aging signals (duplication, abandoned modules, unclear ownership, etc.) over time?

  2. Has anyone built a non-blocking feedback loop that surfaces technical debt without slowing releases?

  3. How much codebase visibility do non-engineering stakeholders get, if any?

  4. Do DevOps practices in your experience reduce, surface, or sometimes hide long-term code risk?

  5. Are there frameworks or methodologies you follow for communicating software health beyond operational metrics?

I’ve been exploring different approaches and tools in this space (including some newer platforms focusing on code risk + valuation), so I’m really interested in hearing how real teams handle it what works, what doesn’t, and what you wish existed. Curious to learn from diverse environments, especially enterprise or compliance-heavy teams.


r/DevOpsLinks • • May 29 '24

Continuous integration The exodus from GitHub Actions to Buildkite

Thumbnail
blacksmith.sh
0 Upvotes

r/DevOpsLinks • • Feb 28 '22

DevOps My company is hosting a webinar this Wednesday at 2pm (EST). If you're curious at all about what ephemeral environments are or what they can do for your team, check it out. See link below to register

0 Upvotes

Click here to reserve your spot.

Discover

• Why teams are moving from long-lived to ephemeral environments

• Common problems teams face in adoption


r/DevOpsLinks • • Apr 23 '24

AIOps Thoughts? Why enterprise AI projects are moving so slowly

6 Upvotes

Fascinating post from the KitOps guys covering the friction in the AI project deployment process–originally published on Dev. to but Reddit hates those links, so I just copy/pasted.

Has anyone tried KitOps?

/////

In AI projects the biggest (and most solvable) source of friction are the handoffs between data scientists, application developers, testers, and infrastructure engineers as the project moves from development to production. This friction exists at every company size, in every industry, and every vertical. Gartner’s research shows that AI/ML projects are rarely deployed in under 9 months despite the use of ready-to-go large language models (LLMs) like Llama, Mistral, and Falcon.

Why do AI/ML projects move so much slower than other software projects? It’s not for lack of effort or lack of focus - it’s because of the huge amount of friction in the AI/ML development, deployment, and operations life cycle.

AI/ML isn’t just about the code

A big part of the problem is that AI/ML projects aren’t like other software projects. They have a lot of different assets that are held in different locations. Until now, there hasn't been a standard mechanism to package, version, and share these assets in a way that is accessible to data science and software teams alike. Why?

It’s tempting to think of an AI project as “just a model and some data” but it’s far more complex than that:

  • Model code

  • Adapter code

  • Tokenizer code

  • Training code

  • Training data

  • Validation data

  • Configuration files

  • Hyperparameters

  • Model features

  • Serialized models

  • API interface

  • Embedding code

  • Deployment definitions

Parts of this list are small and easily shared (like the code through git). But others can be massive (the datasets and serialized models), or difficult to capture and contextualize (the features or hyperparameters) for non-data science team members.

Making it worse is the variety of storage locations and lack of cross-artifact versioning:

  • Code in git

  • Datasets in DvC or cloud storage like AWS S3

  • Features and hyperparameters in ML training and experimentation tools

  • Serialized models in a container registry

  • Deployment definitions in separate repos

Keeping track of all these assets (which may be unique to a single model, or shared with many models) is tricky...

Which changes should an application or SRE team be aware of?

How do you track the provenance of each and ensure they weren’t accidentally or purposefully tampered with?

How do you control access and guarantee compliance?

How does each team know when to get involved?

It’s almost impossible to have good cross-team coordination and collaboration when people can’t find the project’s assets, don’t know which versions belong together, and aren’t notified of impactful changes.

I can hear you saying... “but people have been developing models for years...there must be a solution!”

Kind of. Data scientists haven't felt this issue too strongly because they all use Jupyter notebooks. But…

Jupyter notebooks are great...and terrible

Data scientists work in Jupyter notebooks because they work perfectly for experimentation.

But you can’t easily extract the code or data from a notebook, and it’s not clear for a non-data scientist where the features, parameters, weights, and biases are in the notebook. Plus, while a data scientist can run the model in the notebook on their machine, it doesn't generate a sharable and runnable model that non-data science teams can use.

Notebooks are perfect for early development by data scientists, but they are a walled garden, and one that engineers can’t use.

What about containers?

Unfortunately, getting a model that works offline on a data scientist’s machine to run in production isn’t as simple as dropping it into a container.

That’s because the model created by a data science team is best thought of as a prototype. It hasn’t been designed to work in production at scale.

For example, the features it uses may take too long to calculate in production. Or the libraries it uses may be ideally suited to the necessary iterations of development but not for the sustained load of production. Even something as simple as matching package versions in production may take hours or days of work.

We haven't even touched on the changes that are likely needed for logging and monitoring, continuous training, and deployment pipelines that include a feedback loop mechanism.

Completing the model is half the job, and if you’re waiting until the model is done to start thinking about the operational needs you’ll likely lose weeks and have to redo parts of the model development cycle several times.

Bridging the divide between data science and operations

In my previous roles at Red Hat and Amazon Web Services, I faced a dilemma familiar in many tech organizations: an organizational separation between data science and operations teams.

As much as the data scientists were wizards with data, their understanding of deploying and managing applications in a production environment was limited. Their AI projects lacked crucial production elements like packaging and integration, which led to frequent bottlenecks and frustrations when transitioning from development to deployment.

The solution was not to silo these teams but to integrate them. By embedding data scientists directly into application teams, they attended the same meetings, shared meals, and naturally understood that they (like their colleagues) were responsible for the AI project’s success in production. This made them more proactive in preparing their models for production and gave them a sense of accomplishment each time an AI project was deployed or updated.

Integrating teams not only reduces friction but enhances the effectiveness of both groups. Learning from the DevOps movement, which bridged a similar gap between software developers and IT operations, embedding data scientists within application teams eliminates the "not my problem" mindset and leads to more resilient and efficient workflows.

There’s more...

Today, there are only a few organizations that have experience putting AI projects into production. However, nearly every organization I talk to is working on developing AI projects so it’s only a matter of time before those projects will need to live in production. Sadly, most organizations aren’t ready for the problems that will come that day.

I started Jozu to help people avoid an unpleasant experience when their new AI project hits production.

Our first contribution is a free open source tool called KitOps that packages and versions AI projects into ModelKits. It uses existing standards - so you can store ModelKits in the enterprise registry you already use.

📷📷


r/DevOpsLinks • • Jul 31 '23

DevSecOps Secrets Made My Life Miserable - Consume Secrets Easily With Teller

Thumbnail
youtu.be
3 Upvotes

r/DevOpsLinks • • Jun 18 '25

Kubernetes [Shameless Workshop invitation] Resource-based: Choosing the Right Scaling Approach for K8s Workloads

Thumbnail
info.perfectscale.io
0 Upvotes

LIVE WORKSHOP

Event-driven vs. Resource-based: Choosing the Right Scaling Approach for K8s Workloads

Tuesday, June 24, 2025 | 12:00PM EST

Join us for a practical, hands-on session where we dig into the real-world challenges of Kubernetes autoscaling—and how to solve them with event-driven scaling and intelligent optimization.


r/DevOpsLinks • • Mar 29 '26

DevOps 🚀 I Built an Open-Source React Native CICD Workflow Builder — No More YAML Hell

Post image
0 Upvotes

r/DevOpsLinks • • Apr 30 '25

DevOps Is this the best course to help me level up

0 Upvotes

I am thinking about taking the SANS GCSA (https://www.sans.org/cyber-security-courses/cloud-native-security-devsecops-automation/ )course ( sponsored by my job) I have about 2 years experience in IT and one year of software engineering have good understanding of fundamentals of GitHub and pipeline. I am trying to get into devops I was wondering whether we are allowed to put the projects from this course on our resume and can we do them on how personal GitHub. And also would it be comprehensive enough to help me break into devsecops.


r/DevOpsLinks • • Aug 25 '23

Monitoring and observability Parsing logs with the OpenTelemetry Collector, working on a series of guides on collector configuration

Thumbnail signoz.io
0 Upvotes

r/DevOpsLinks • • Mar 27 '22

Kubernetes Kubernetes Resource Consumption Statistics at your Fingertips

0 Upvotes

Here's how to quickly collect Kubernetes resource usage data without installing monitoring agents: [link](https://dev.to/otomato_io/kubernetes-statistics-in-your-console-4182)


r/DevOpsLinks • • Mar 15 '22

DevOps Adoption of DevOps at HMRC

0 Upvotes

Hello!

We would like to invite you to our Tech Series with Ben Conrad, Head of Agile Delivery for MDTP who will examine the role of DevOps at HMRC, how they have been able to deliver digital tax services frequently while learning from incremental successes and failures. Ben will talk about the ‘You Build It You Run It’ approach and how they are utilising DevOps to their advantage to foster a mature DevOps culture at HMRC.

He’ll also share the challenges that come with its wider legacy estate and implementing DevOps, particularly in a government organisation.

When: 23rd, March 12pm GMT

Where: Online Save your place here: https://esynergy.co.uk/event/techseries-devops-hmrc/


r/DevOpsLinks • • Aug 25 '24

DevOps Link to any 90 Days DevOps Challenge?

0 Upvotes

Is there any 90 Days DevOps Challenge to improve oneself in DevOps technologies?


r/DevOpsLinks • • Feb 13 '25

Containerization Top 5 Books to Learn Docker for Beginners in 2025 - Best of Lot

Thumbnail
javarevisited.blogspot.com
0 Upvotes

r/DevOpsLinks • • Dec 14 '18

DevOps Trends for 2019: Five Areas to Watch Out For

Thumbnail
squadex.com
0 Upvotes

r/DevOpsLinks • • Jan 23 '23

DevOps DevOps is Dead !?

Thumbnail
youtube.com
0 Upvotes

r/DevOpsLinks • • Jan 31 '23

DevOps Ansible vs. Jenkins: What's the Difference?

Thumbnail
phoenixnap.com
0 Upvotes

r/DevOpsLinks • • Jan 18 '23

DevOps The Key to Success as a DevOps Engineer

Thumbnail
youtu.be
0 Upvotes

r/DevOpsLinks • • Aug 22 '18

Enhance Your DevOps Tool Chain to Support Organizational Growth

Thumbnail
technology.org
0 Upvotes

r/DevOpsLinks • • Dec 30 '20

AWS - NGINX: Load Balancing in the Cloud

Thumbnail
youtu.be
0 Upvotes

r/DevOpsLinks • • May 12 '22

DevOps How To Become A DevOps Engineer?

0 Upvotes

A DevOps engineer is a good career choice in 2022 as the demand for it is increasing considerably. The need for a skilled DevOps engineer is expanding within the market. But there are still some misconceptions and confusions regarding this career choice. Well, let's dig into this article to clear your doubts and confusion regarding DevOps engineers.

In this technology-driven era where information and data are fed into computers, almost every company is implementing cloud services to maintain their working professional environment. Learning DevOps is necessary if you are an aspirant with an IT background who aspires to be a part of the IT sector. Let's go from the basics to understand the career path of a DevOps engineer.


r/DevOpsLinks • • Jul 15 '21

DevOps Github Copilot: Microsoft's Advanced Investment in Automatic Coding

Thumbnail thechief.io
0 Upvotes

r/DevOpsLinks • • Jul 15 '21

DevOps Code Quality and Security Ensured With CI/CD Experience for Github Actions

Thumbnail thechief.io
0 Upvotes

r/DevOpsLinks • • Nov 20 '22

Containerization Introduction to Docker: A Beginners Guide

Thumbnail
karanjagtiani.medium.com
0 Upvotes

r/DevOpsLinks • • Jun 24 '23

DevOps Breaking Barriers: How AI is Changing the Game in Future DevOps (waiting to be approved on reddit)

0 Upvotes

Hey folks! Today, let's talk about the future of DevOps and how it's getting a major makeover with AI. It's mind-blowing stuff, so let's dive in!

Imagine a world where DevOps becomes supercharged, like it's on steroids. We're heading there, my friends, and it's all thanks to the awesome integration of AI technologies. We're about to witness a radical revolution in how we develop, deploy, and manage software. Buckle up!

Now, let's tackle the never-ending battle of serverless vs. containers. With the magic of AI-powered DevOps tools, we can make smarter decisions on workload distribution and optimization. It's like having a genius DevOps guru in your corner, guiding you on whether to go serverless or stick with containers. Talk about having a secret weapon!

But wait, there's more! AI is leveling up the game when it comes to monitoring and troubleshooting in DevOps. Those slick machine learning algorithms can sniff out anomalies, predict failures, and even give you tips on how to prevent problems. Say goodbye to sleepless nights and hello to more time for innovation and making magic happen.

Plus, AI isn't just about automation; it's boosting collaboration too. By crunching data from different sources, it helps teams communicate better and make smarter decisions. It's like having a universal translator for developers, operations peeps, and security wizards. AI is tearing down walls and creating a united front.

So, my friends, brace yourselves for the mind-blowing future of DevOps, powered by AI. From optimizing workloads to keeping a watchful eye on things and fostering team unity, AI is shaking things up like never before. Get ready to ride the AI wave into the future of DevOps—it's going to be wild! 🚀🔥