This is a quick update on new features and improvements on CSv2, our Kubernetes backed container stacks:
Feature Parity
We are getting closer to feature parity between CSv2 and our v1 Container Stacks. This has been completed for all service.yml attributes with the exception of the following deprecated elements:
services/pre_start_signal
services/add_to_lb
services/privileged
services/constraints/servers
services/resources
services/requires
services/restart_on_deploy
Please note that using version: 2 at the top of your service.yml is needed for CSv2.
We are now working on bringing our API and Toolbelt to support CSv2.
Kubernetes node labels
You can now use a key=value format in server tags and they will be synched with Kubernetes nodes. This can be used for node selection for different services.
Shell into the container right from the web
This is a cool feature that allows you to shell into a running container right from the web UI.
Switching to dedicated or shared Kubernetes Master node
When you start a new CSv2 stack, you usually have only 1 server. This will be used as the Kubernetes Master node but also takes on your application workload. Ideally, you would want to have dedicated Master nodes to take care of managing your cluster and put your workload on other "worker" nodes. This is now as easy as clicking a button in the UI!