Introduction to SUSE Container as a Service (CaaS) platform v3

Over the years, SUSE has been developing more and more innovative and front running technologies, focusing mainly on making the tech available as a platform in order to provide a way to manage and maintain installations. This is nothing new, most Linux vendors do this. we call it wrapping something around a technology to make it more usable without actually changing the underlying tech.

So what is SUSE Container as a Service? Its a great platform to deploy and manage a full fledged Kubernetes cluster without any regards of size. Pretty cool? I thought so too.

Now, what is kubernetes? It is the container orchestration engine made by Google. An orchestration engine allows you to basically write a single template and tell the cluster what you want and it will build this for you in very short time. It’s fully reproducible, so you don’t have to re-install manually anything and its very quick due to the nature and size of containers.

It allows you to run containerized services in a controlled and production ready manner and in a sense takes the whole “IT Operations” out of the Development cycle… In a sense 😀

Another question on your mind: What really is a container? First off, in Kubernetes / SUSE CaaS speak they are pods, not containers. Well a Container is a static application or service image, that means there is no moving parts and nothing can be saved into it, that can be deleted, updated and relaunched at any time, simply BECAUSE it has no real data. For example, you could have a php application that accesses a database to display a webpage. If everything is stored in the database and nothing inside the application directory like files etc., you containerize that applications, make it run and access the database.

And now the golden question: why Containers? Simple: Simplicity, quick development, and ease of use.  Most people flaunt new tech with buzz words like “secure”  and #Security aware”. well containers aren’t. They are not INSECURE either, they are static and in being static you can whitelist or control them according to your needs. But that all depends on your strategy. However when we come to SUSE CaaS, and the kubernetes platform, there are quite a few security features built in right out of the box. These include mandatory SSL communication between nodes, Role based access for a user to launch containers etc. These all need to be configured at some point if you install Kubernetes from scratch but with SUSE CaaS they are already included.

Comments are closed.