Intelligent CIO Middle East Issue 81 - Page 76

t cht lk

t cht lk

Michael Cade , Senior Technologist Product Strategy at
Veeam Software
The containers created in Docker can each exist and be worked on separately . Developers can manage them individually and do not necessarily need a higher-level solution to manage them . But with the number of containers , the complexity grows and the overview is lost .
To keep this effort small and as clear as possible , a central administration point must be set up – and this is where Kubernetes comes into play . The software keeps an eye on everything and ensures , for example , that payloads are distributed dynamically and sensibly to the containers to guarantee the availability of a service and ensure that it can meet all requirements .
Kubernetes is thus an orchestration for Docker and accordingly , a connection between the two is not only possible but desirable .
New security vulnerabilities in sight ?
The latter first look at what this is all about , whether it can be incorporated into their networks and be useful at all to gain an advantage in the market . On the side , however , these entrepreneurs are busy with other trends that they need to take a closer look at , such as cloud Infrastructure-as-a-Service .
Compatible with the runtime environments ?
Of course , the question immediately arises as to whether Kubernetes and the virtualization software are compatible . First , let ’ s set the record straight about exactly what we are talking about : Kubernetes is an orchestration system for containers ; Docker for example , is for now the most common container runtime .
Kubernetes does not change the threat landscape . It does not close security gaps but requires the same Modern Data Protection as any other type of data . Formerly , we just saved everything , then with virtualization we selected what to protect and how often .
Today , we move forward with containers that sometimes only last for minutes or hours , other than virtual machines that can have a lifetime of months . Kubernetes . io provides in-depth documentation that focuses on the ‘ Four Cs ’ of cloud-native security : Code ; Container ; Cluster ; Cloud / Corporate Data Center .
It states that each layer of the cloud-native security model builds on the previous one . Accordingly , the coding layer ( code layer ) benefits from a strong foundation at the cloud , cluster and container level . So , if weak IT security standards apply there , the
76 INTELLIGENTCIO MIDDLE EAST www . intelligentcio . com