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

Create an application by using an image

If you create an application in the Container Service console by using an image, the Swarm cluster Web interface is different from the Kubernetes cluster Web interface.

Basic information

Container Service Swarm clusters

The basic information for creating an application in a Swarm cluster includes the application name, application version, deployment cluster, default update policy, and application description.

Container Service Kubernetes clusters

The basic information for creating an application in a Kubernetes cluster includes the application name, application version, deployment cluster, namespace, number of replicas, and application type.

The namespace term is exclusive to Kubernetes clusters. Kubernetes uses namespaces to isolate resources such as CPU and memory. In addition, namespaces can be used to separate different environments such as test and development environments. We recommend that you use clusters to isolate production environments. For information about the namespace term, see Terms.



General settings

The image name and image version settings are the most important.

Container Service Swarm clusters

The Network Mode supportsDefault and host.

Container Service Kubernetes clusters

  • The network mode of the application has been specified when you create the cluster. Available network plugins include Flannel and Terway. For more information, see Do I select the Terway or Flannel plugin for my Kubernetes cluster network?.
  • Required resources include the CPU and memory resources required by the application. The resource limits are the upper thresholds of the resources quota. You can compare the settings with the CPU Limit and Memory Limit settings of the Container settings in a Swarm cluster.