How the CNCF Grapples with Continuous Integration and Deployment

Apr 10th, 2017 3:00pm by Alex Williams

For today’s episode of The New Stack Makers podcast, we sat down with Chris Aniszczyk, chief operating officer for the Cloud Native Computing Foundation, at CloudNativeCon/KubeCon Europe 2017 conference in Berlin last month. We spoke with Aniszczyk about the pros and cons of having two container runtimes, rkt and containerd, managed by the CNCF at the same time. Another topic of discussion was the ever-growing presence of continuous integration and continuous deployment (CI/CD), and how those practices are evolving for the CNCF Technical Oversite Committee as it looks toward accepting future projects to the Foundation.

Exploring the Latest Container Runtime Projects in the CNCF

Also available on Apple Podcasts, Google Podcasts, Overcast, PlayerFM, Pocket Casts, Spotify, Stitcher, TuneIn

Topics

1:05: About the CNCF ToC.
1:42: The rationale for two runtimes in the cloud native ecosystem.
3:15: The purpose of containerd.
4:47: How rkt is a different container technology.
5:51: How companies are thinking about containerd and rkt.
6:37: The need for compatibility between containerd and rkt.
7:31: Other projects within the CNCF.
9:16: On the subject of CNCF producing a single stack.
10:26: How to ToC is working with CI/CD.

The Cloud Native Computing Foundation sponsored this podcast.

Alex Williams is founder and editor in chief of The New Stack. He's a longtime technology journalist who did stints at TechCrunch, SiliconAngle and what is now known as ReadWrite. Alex has been a journalist since the late 1980s, starting...