ADDO 2019 DevOps in a containerized world
1 like•788 views
DevOps in a containerized environment emphasizes the need for collaboration, automation, and shared responsibilities among development, security, and operations teams. The document discusses the complexities introduced by containerization, including the need for orchestration, monitoring, and a cultural shift in how teams operate. It highlights the importance of integrating tools, understanding infrastructure changes, and adapting to a more agile approach to maintain performance and availability.
ADDO 2019 DevOps in a containerized world
- 2. DevOps in a containerized world Martin Alfke - example42 GmbH
- 3. Agile Development -> Faster Release Cycles Collaboration and automation required Everybody is a trusted and honest customer Classical DevOps Image: tatlin
- 4. Product is customer for Dev Dev is customer for Ops Everybody is customer for Sec ProdDevSecOps or DevOps Classical DevOps Image: tatlin
- 5. DevOps KATA - (K)Culture Classical DevOps Image: tatlin
- 6. DevOps KATA - (K)Culture - Automation Classical DevOps Image: tatlin
- 7. DevOps KATA - (K)Culture - Automation - Transparency Classical DevOps Image: tatlin
- 8. DevOps KATA - (K)Culture - Automation - Transparency - Agility Classical DevOps Image: tatlin
- 9. Shared tooling (where useful and possible) - Version Control - Configuration Management - Secrets Management Classical DevOps Image: tatlin
- 10. Shared tooling (where useful and possible) - VM Management - Metrics - CI/CD/CD System Classical DevOps Image: tatlin
- 11. Shared responsibility - Hardware - OS - Application Classical DevOps Image: tatlin
- 12. Hard learning curve: - GIT (rebase, squash, merge) - API driven infrastructure - Change fast and early - Paradigm Change Classical DevOps Image: tatlin
- 13. Cloud adds Finance! - Budget - Spending overview and forecast - Invoicing Tooling remains the same ProdDevSecFinOps Cloud DevOps Image: tatlin
- 14. Standarized Systems Setup On-premise or off-premise Private or public cloud Collaborative setup, management and maintenance Classical and Cloud DevOps Image: tatlin
- 15. DevOps and Containers Dev learned complexity of systems and application Separation of concerns: - Ops manages OS and DC - Dev manages App (incl. deployment, monitoring, metrics, alerting) Image: tatlin
- 16. DevOps and Containers Container infrastructure: - SDN is absolute must - Containers need orchestration - Monitoring on services, not systems Image: tatlin
- 17. DevOps and Containers - New thinking on infrastructure and applications required (Dev, Sec, Net and Ops) - Time to learn new concepts, technology and automation Image: tatlin
- 18. DevOps and Containers Why containers? - Cloud compatible - more easy to migrate - Dev can isolate issues within applications - Ops can isolate issues within infrastructure Image: tatlin
- 19. DevOps and Containers - Dev only needs CI/CD/CD, Registry and CR or CO API - Dev responsible for staging and reverting via API calls/health checks - Dev responsible for performance and availability (of applications) Image: tatlin
- 20. DevOps and Containers - Ops responsible for sizing and storage - Ops responsible for access using tokens to namespaces with hardware limits set - Fin responsible for budget Image: tatlin
- 21. DevOps and Containers - Sec provides policies on containers (cgroups, Kernel capabilities) - Net builds interconnect between Layer 1 and SDN - Sec supports all security aspects: Network, Servers, Application Image: tatlin
- 22. DevOps and Containers How about: - Tooling decisions - Secrets - Infrastructure decisions Image: tatlin
- 23. DevSecOps: - nothing is stand alone - security brings everybody together - KATA Image: tatlin DevOps and Containers
- 24. How much Ops would you still like to do? Maybe private cloud with "opsless" and "serverless" is an option (start-up mentality). What about heritage platform? Image: tatlin DevOps and Containers
- 25. Summary “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
- 26. Summary DevOps in a containerized world is not dead. It is even more required compared to heritage systems. Steep learning curve for everybody (Dev, Sec, Ops, Net, Fin, Mgmt). Image: tatlin
- 28. Conclusion Find tools which integrate properly (REST API) Prevent NIHS (not invented here syndrome) Image: tatlin
- 30. Conclusion
- 31. Conclusion “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
- 32. DevOps in a containerized world Martin Alfke - example42 GmbH