Containership Kubernetes Engine (CKE) Updates
We are pleased to announce that the Containership Kubernetes Engine recently passed conformance testing for Kubernetes 1.12.x and is now certified on the latest minor release. Doing so, CKE continues to be a leader in conformance testing for Kubernetes releases. The latest certification makes upgrading CKE clusters from previous versions a one-click process from within the Containership dashboard. Read more on some of the new features that come along with 1.12.x on the official Kubernetes blog.
Workload Creation Tool
Kubernetes is notoriously complex, leaving many users to struggle with seemingly simple tasks such as launching a Ghost blog. Kubernetes is an entire container orchestration system, creating the building blocks for extensive infrastructure management through the use of resources like Deployments and DaemonSets. You just want to launch an application, but now you are wrestling with Controllers, Pods and complex YAML not truly meant to be edited by hand. Here at Containership we encountered this problem firsthand and have built a tool that guides you through the creation process, while still enabling you to take advantage of all the complexities Kubernetes has to offer. First, we will quickly summarize some key Kubernetes terminology you need to understand:
Container: A container is a standard unit of software that packages up code and all its dependencies so the application can run reliably from one environment to the next.
Pod: Group of containers bundled together that run on the same host, in the same networking space.
Controller: Kubernetes construct that is responsible for managing one or more Kubernetes resources.
Deployment: Kubernetes controller that manages pods and revisions between them as it updates.
DaemonSet: Kubernetes controller that manages pods required to run one or more times on every node in your cluster.
Workload: Any Kubernetes controller that manages one or more pods. An example of a workload is a Deployment or DaemonSet for instance.
Our team built a step by step workload creation wizard which guides users when creating workloads. It does this without sacrificing power, allowing users to see and edit the raw YAML created under the hood at any step along the way. This gives you the best of both worlds, a simple way to create workloads, while still being able to understand how options map into the native Kubernetes readable syntax.
The creation wizard consists of five distinct steps:
1. Workload Details: Choose the cluster, namespace, and type of workload you want to launch.
2. Add Containers: Choose details about the containers running in your workload, including easy addition of private registry information.
3. Add Volumes: Add mounted volume details for your containers.
4. Scheduling: Choose how your workload will be scheduled onto the nodes of your cluster.
5. Summary: Overview of the selected options for launching your workload.
Resource Creation Templates
If you are not in need of a wizard to launch your resources, Containership now also features a handy tool for those well versed in YAML. With our new Resource Templates feature end users can utilize pre-made templates when creating CronJobs, Deployments, Pods, or ReplicaSets. This will help save time and help developers easily stand up resources on their Kubernetes clusters without starting from scratch. The resource templates can be accessed from the Containership dashboard. Hit the
Create button, and then select
From there, select the target clusters and then select the resource type. As you toggle through the types, the editor will update with the appropriate template. Once you select the correct resource type, you can begin editing the template from within the YAML editing window to configure your service. Once you are satisfied with your new settings you are ready to launch your resource!
The new workload creation UI, 1.12.x clusters and Resource Templates are available today. If you have not already signed up for Containership, please come check it out and let us know what you think. We hope this begins to help ease the transition for new users into Kubernetes.