Why DevSecOps is Just a Fancy Acronym for Kubernetes Service Ownership

Written By: Joe Pelletier

The Rise of DevSecOps

Historically, software development has consisted of several teams, all working towards a singular goal-to produce excellent products. Despite this shared effort, the development process itself has typically employed a siloed approach, where one team of developers writes the code, a quality assurance team tests the code, and another operations team deploys it to production. Nowadays, a security team must also weigh in to ensure the quality and security of software meets all modern standards and governance requirements.

The Reality of Service Ownership

DevSecOps is not the only way to describe this emerging model of accountability. As a DevOps philosophy of “code it, ship it, own it,” Kubernetes service ownership asks engineers to be responsible for the code and services they hold, from code commit to production to deployment. Instead of tossing code to operations or depending on the reliability engineering (SRE) team, engineers are responsible for the security and reliability of the code they create-from start to finish.

A Better Way Forward

To learn more about the essential elements of Kubernetes service ownership and how Fairwinds Insights can enable a more manageable experience for your organization, read our Complete Guide to Kubernetes Service Ownership.

--

--

Fairwinds — The Kubernetes Enablement Company | Editor of uptime 99

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Fairwinds

Fairwinds — The Kubernetes Enablement Company | Editor of uptime 99