DevOps describes the culture of communication and collaboration between IT Development and IT Operations departments. Usually this covers system setup, application deployment and all the surrounding tools like CI, metrics and alerting. A core element has always been IT automation using configuration management and CI/CD. But how do we do DevOps in a containerized world? Do we still need configuration management? Is there still collaboration possible? Or iare containers the DevOps killer? In my talk I draw a picture on responsibilities, does and don’ts when it comes to developers and operations working within a container runtime platform. I want to show where we still have DevOps and where we pass responsibilities to a single department only and what kind of security borders we have at hand to work separately but with trust.

1. DevOps in a containerized world
Martin Alfke - example42 GmbH

2. DevOps in a containerized world - OSDC 2019 - Martin Alfke © example42 GmbH !2
Agile Development -> Faster Release
Cycles
Collaboration and automation required
Everybody is a customer
Classical DevOps

3. DevOps in a containerized world - OSDC 2019 - Martin Alfke © example42 GmbH !3
Product is customer from Dev
Dev is customer from Ops
Sec is customer for all
DevOps
Classical DevOps

4. DevOps in a containerized world - OSDC 2019 - Martin Alfke © example42 GmbH !4
DevOps KATA
- Kultur
- Automatisierung
- Transparenz
- Agilität
Classical DevOps

5. DevOps in a containerized world - OSDC 2019 - Martin Alfke © example42 GmbH !5
Shared tooling (where possible)
- Version Control
- Metrics
- CI System
Classical DevOps

6. DevOps in a containerized world - OSDC 2019 - Martin Alfke © example42 GmbH !6
Shared responsibility
- Hardware
- OS
- Application
Classical DevOps

7. DevOps in a containerized world - OSDC 2019 - Martin Alfke © example42 GmbH !7
Tooling
- GIT
- VM Management
- Configuration Management
- Secrets Management
- CI/CD/CD
Classical DevOps

8. DevOps in a containerized world - OSDC 2019 - Martin Alfke © example42 GmbH !8
Hard learning curve:
- GIT (rebase, squash, merge)
- API driven infrastructure
- Paradigm Change
Classical DevOps

9. DevOps in a containerized world - OSDC 2019 - Martin Alfke © example42 GmbH
DevOps and Containers
!9
Image: wikimedia.org
Dev understand complexity of systems
and application
Separation of concerns:
- Ops manages OS and DC
- Dev manages App (incl. deployment,
monitoring, metrics, alerting)

10. DevOps in a containerized world - OSDC 2019 - Martin Alfke © example42 GmbH
DevOps and Containers
!10
Image: wikimedia.org
Problem:
- Container need other infrastructure
- SDN is absolute must
- Container need orchestration
- Monitoring on services, not systems

11. DevOps in a containerized world - OSDC 2019 - Martin Alfke © example42 GmbH
DevOps and Containers
!11
Image: wikimedia.org
Downside:
- Infrastructure is different
(completely?)
- New thinking on infrastructure and
applications required (both Dev and
Ops)
- Time to learn new concepts,
technology and automation

12. DevOps in a containerized world - OSDC 2019 - Martin Alfke © example42 GmbH
DevOps and Containers
!12
Image: wikimedia.org
Benefits:
- Cloud compatible infrastructure -
more easy to migrate
- Dev can isolate issues within
applications
- Ops can isolate issues within
infrastructure

13. DevOps in a containerized world - OSDC 2019 - Martin Alfke © example42 GmbH
DevOps and Containers
!13
Image: wikimedia.org
Benefits:
- Security policies on containers
needed (cgroups, Kernel capabilities)

14. DevOps in a containerized world - OSDC 2019 - Martin Alfke © example42 GmbH
DevOps and Containers
!14
Image: wikimedia.org
- Secrets are shared responsibility
- Dev only needs CI/CD/CD, CRI API,
no shared infrastructure
- Dev responsible for staging and
reverting via API calls/health checks
- Ops responsible for Scaling, Network
and Storage

15. DevOps in a containerized world - OSDC 2019 - Martin Alfke © example42 GmbH
DevOps and Containers
!15
Image: wikimedia.org
- Dev responsible for CPU and memory
limits on containers
- Tooling decisions
- Dev responsible for performance and
availability (of applications)

16. DevOps in a containerized world - OSDC 2019 - Martin Alfke © example42 GmbH
DevOps and Container Orchestration
!16
Multiple nodes where Containers can
run.
Managed by an orchestration.
Image: tatlin

17. DevOps in a containerized world - OSDC 2019 - Martin Alfke © example42 GmbH
DevOps and Container Orchestration
!17
Ops:
- manages core cluster, hardware or
VM, network (SDN), Storage, Ingress
and Egress and SSL off-loading.
- provides access using tokens to
namespaces with hardware limits set
for Dev teams
Image: tatlin

18. DevOps in a containerized world - OSDC 2019 - Martin Alfke © example42 GmbH
DevOps and Container Orchestration
!18
Dev:
- handles application deployment and
updates within its namespace(s) and
ensures that containers have
hardware limits set
- Secrets can still be shared
responsibility
Image: tatlin

19. DevOps in a containerized world - OSDC 2019 - Martin Alfke © example42 GmbH
DevOps and Container Orchestration
!19
How much Ops would you still like to
do?
Maybe cloud and "opsless" and
"serverless" is an option (start-up
mentality).
Still have on-prem? Still do DevOps!
Image: tatlin

20. DevOps in a containerized world - OSDC 2019 - Martin Alfke © example42 GmbH
Summary
!20
Simple can be harder than complex: You have to work hard to
get your thinking clean to make it simple. But it's worth it in the
end because once you get there, you can move mountains. -
Steve Jobs

21. DevOps in a containerized world - OSDC 2019 - Martin Alfke © example42 GmbH
Summary
!21
• DevOps in a containerized world is
not dead.
• It is even more required compared
to standard systems.
• Steep learning curve for everybody
(Dev, Sec, Ops, Mgmt).
Image: tatlin

22. DevOps in a containerized world - OSDC 2019 - Martin Alfke © example42 GmbH
Summary
!22
• Benefits can be TTM, TCO.
• Requires CI/CD/CD !!
• Automate everything.
Image: tatlin

23. DevOps in a containerized world - OSDC 2019 - Martin Alfke © example42 GmbH
Conclusion
!23
Image: tatlin

24. DevOps in a containerized world - OSDC 2019 - Martin Alfke © example42 GmbH
Conclusion
!24
“I used to think that top environmental problems were biodiversity loss, ecosystem
collapse and climate change. I thought that thirty years of good science could
address these problems. I was wrong. The top environmental problems are
selfishness, greed and apathy, and to deal with these we need a cultural and
spiritual transformation. And we scientists don’t know how to do that.”
Gus Speth, March 2016

25. DevOps in a containerized world
Martin Alfke - example42 GmbH