Shipping With Kubernetes on Replicated

A quick overview of how to get started with Kubernetes and Replicated.

Replicated can be used with a Kubernetes application to deploy an enterprise-installable version of your application. Replicated is a platform that adds functionality to an application to allow for easy behind-the-firewall installation and integration into enterprise systems. When using Replicated with Kubernetes, developers have the ability to reuse most of the existing Kubernetes specs and Replicated will be responsible for installing and maintaining a Kubernetes cluster for the enterprise installation.

When to use the Kubernetes Scheduler

Compared to other schedulers supported by Replicated, Kubernetes offers:

  • Native Kubernetes experience, including the ability to ship and reuse existing Kubernetes specs
  • Automatic provisioning of a Kubernetes cluster on any supported operating system
  • Standard Kubernetes functionality including cluster-wide DNS resolution and load balancing

When to Use Other Schedulers

There are cases where using other schedulers, such as the Replicated Native scheduler or Docker Swarm provides a better experience.

  • Some enterprises require the use of Long Term Support Operating Systems in the 2.x kernel series such as RedHat Enterprise Linux 6. Replicated with Docker Swarm requires Docker 17.03 or later, while RHEL6 only supports Docker 1.7.1. To support RHEL 6 and older versions of Docker, consider the Replicated Native Scheduler.
  • If existing Kubernetes specs are not available, writing them only to support an enterprise installation might take extra time. In this case, the learning curve of Docker Swarm could be a good choice.

Overview

The process to ship your application in Replicated consists of the following steps:

  1. Create a vendor account on the Replicated Vendor Portal.
  2. Prepare the images required by your app. You can either:
    • Tag and push your images to the Replicated Private Registry. Or
    • Select images from a public registry ie Docker Hub. Or
    • Push your images to a third party private registry & provide Replicated with access.
  3. Define your components on the Replicated Vendor Portal.
  4. Create a release of your application.
  5. Install your application to test.