This topic compares the container and label settings used in a Swarm cluster with those used in a Kubernetes cluster for creating an application through an image.

Create an application by using an image

When you create an application in the Container Service console by using an image, you will see that the Web interfaces are different in a Swarm cluster and a Kubernetes cluster.

Container settings

Container Service Swarm clusters

You can set container startup commands (through the Command parameter and the Entrypoint parameter), resource limits (including CPU Limit and Memory Limit), Container Config, and other parameters.

Container Service Kubernetes clusters

The Container settings of the Swarm cluster are similar to the life cycle settings and some general settings of the Kubernetes cluster.


Container Service Swarm clusters

With labels, you can set health checks, access domain names, logs, and other functions.

Container Service Kubernetes clusters

A label can only mark an application in a Kubernetes cluster. Different methods are used in a Kubernetes cluster to implement the functions that are implemented through labels in a Swarm cluster, such as health checks and access domain names.

When you create an application in a Kubernetes cluster by using an image, a label of the same name as the application is created. The label is not displayed on the application configuration page. You can use labels in YAML files.