Kubernetes provides a lot of security features, but securing your setup can be complex and vulnerabilities are often not discovered.
Starting from the Linux namespaces used in containers, all the way to the network, there are a lot of configurations to support (or totally destroy) the security of a cluster.
In this talk, Thomas will cover:
After a 30 minutes talk, there will be 15 minutes for Q&A. We’d like to encourage you to submit your questions in advance.
A recording of the webinar and related materials will be shared with webinar attendees afterwards.
DevOps Engineers, Site Reliability Engineers, System Engineers, Infrastructure Kubernetes Administrators, Technical Architects, Application Developers with an affinity with DevOps and Technical Management.
Thomas Fricke has started Endocode, an Open Source and Cloud company and worked for several years as the CTO.
He is now working as a freelancer mainly as a Security Architect implementing Kubernetes based SecDevOps in Energy and Healthcare. He has a long history in building clouds, is working with Kubernetes nearly from the beginning, and started with Linux 0.95.
Thomas is pro bono member of the Gaia X project, AG Kritis, and member of the German IT Planungsrat (IT steering committee). He also started an initiative to create a legally and technically safe Government repo “Ein Ort für öffentlichen Code” (a place for public code).