2018

EPAM Cloud: Containerization Ecosystem in Few Steps

Containerization has become a buzzword in recent years. This cutting-edge trend is not new in software development, but the methodology is developing quickly, and we can see new tools and approaches appearing regularly.

Naturally, the interest in containerization is also growing, and the number of projects considering or already using it is increasing.

Why is this happening?

Containerization allows running processes and applications in an isolated environment. The virtualization is performed on the OS level, and all containers, though isolated from each other, are run on a single host and use the same kernel. This allows, in many cases, to use resources more effectively than when a whole virtual machine is engaged for a single app.

Among other advantages of the approach, there is improved security resulting from isolation and easy scaling and migration. Any worries related to the mismatch of configurations between different environments are also minimized.

EPAM has always kept up with the times. There are already numerous projects that are migrating to container-based infrastructures or using containers from the start. Naturally, the trend found its way to EPAM Cloud, as it is the company standard for creating development environments. A real Containerization Ecosystem evolved in EPAM Cloud in short order:



Naturally, Docker as a Service, was the pioneer. It allows creating and managing Docker clusters with just a set of simple Maestro CLI commands. In addition, you can create a Docker Registry to store Docker container images and distribute them between nodes.

Kubernetes as a Service was the next step. Kubernetes is used to manage, schedule and run containerized applications created by container engines such as Docker or rkt. With EPAM Cloud, any project team can get Kubernetes up and running quickly and easily.

When the Kubernetes service is activated, you can use it via the native command line interface, kubectl, which is automatically available on the master virtual machine on which Kubernetes is activated. There is also a Web UI that has most of the functionality supported by the CLI in an intuitive format.

In addition, it is possible to connect Kubernetes to the existing Docker registry if needed, which makes the whole approach easier. You can find step-by-step instruction attached to this page.

Finally, OpenShift joined the Orchestrator services family. This is a platform as a service for container management, using Docker containerization and Kubernetes orchestration tools. The service allows deploying the necessary environments in container-based infrastructure, without the need to deep dive into the technical details of container management.

The convenient UI not only allows managing containers, but also includes numerous convenient features that improve infrastructure security, container management and scaling and allow Dev and Ops teams to cooperate effectively.

Of course, one can set up each of these solutions manually. But why spend more time and effort, if most of the work is already done for you? With EPAM Cloud, you can facilitate the containerization of your application and get the necessary tools in automated mode. Your choice depends only on the project?s needs and financial plan.

Make Orchestrator start setting up containers for you and take the free time you get to complete your other tasks or to share your Cloud Services experience in a chat over coffee with your colleagues.

Documentation

Below is a list of documents related to this section. You can find the full list of our documents in the Documentation Storage.

Please select the required document:

Instructions on integrating Docker, Docker Registry and Kubernetes

The document contains detailed instructions on integrating containerization tools into a single system