Rancher
Rancher takes a similar approach to Docker EE when
it comes to deploying a containerization platform,
providing a unified Kubernetes cluster and applica-
tion management platform across a disparate pool of
infrastructure resources (both on-premises and pub-
lic cloud). It also simplifies the management of all the
above under a single control plane. Additionally,
Rancher provides users and platform administrators
with some really useful features, such as RancherOS,
a lightweight container OS, and an application cata-
logue. This lets users manage and deploy entire
multi-container clustered applications with one click
of a button.
The key ethos behind Rancher’s solution is to give
users choice with simplicity. It allows teams to deploy
containers across a variety of infrastructure plat-
forms, and to integrate with a variety of common ser-
vices, such as registries and access control systems.
This is all managed and controlled via a unified con-
trol plane, simplifying administration and operations
with value add components, such as its app catalog
and a complete container management platform that
includes everything you need to manage containers
in production.
Summary, Verdict, Next Steps
The spring of 2018 saw managed container services
being taken seriously by the key public cloud vendors,
with the top two making available their first iteration
of managed Kubernetes as a Service (KaaS). On the
other hand, CaaS solution providers have started
onboarding multiple container orchestrators, provid-
ing users with a choice, using simplified, unified man-
agement tools.
Overall, the current managed Kubernetes services
from Azure and AWS are lacking the core compo-
nents to be ready for prime time and therefore need
still need a rich ecosystem of support tools and ser-
vices. They are, however, a great fit for those looking
to get up and running quickly with Kubernetes, but
who lack the deep expertise and skills required. Goo-
gle is the only provider with a mature and proven
managed container service; however, Google lacks
the wider cloud adoption of the two alternative
providers.
On the other hand, the operational trade-offs one has
to take on when deploying one’s own container
stacks, such as Docker EE and Rancher (amongst oth-
ers), are balanced by their flexibility and maturity.
Additionally, providing a production ready CaaS plat-
form could not be simpler, with the availability of
automated scripts and deployment tools that can
streamline deployment onto virtually any platform.
One should consider some of the following key ques-
tions prior to choosing between a managed container
platform or deploying one’s own:
• Do we have sufficient skills to design, deploy
and administer a Kubernetes environment?
• Does our container platform need to be
deployed on public cloud and on-premises?
• Does the use of a multi-tenanted and shared
Kubernetes control plane have any
implications?
• What is the public cloud platform where I need
to deploy containers? AWS, Azure or Google?
If your company is still in its experimentation stage
with containers, then managed container services
provide a great starting point without having to
worry about cluster management, resource provi-
sioning or having a minimum platform deployed.
Managed container services are great for testing ini-
tial container deployments and tailoring the develop-
ment and operational processes. However, if you are
in a more mature phase of your container deploy-
ment on AWS, Azure or on-premises platforms, then
bringing your own CaaS solution might provide you
with a much more feature rich platform, with all the
necessary frameworks and services required for a
production grade system.
FALL 2018 | THE DOPPLER | 35