Container Service enables you to view and manage the default network of your applications. In addition, you can also create a custom network based on your needs and add applications to the custom network.
When you create a cluster, Container Service creates a default network and an ingress network for system services.
The cluster uses the ingress network for Server Load Balancer. Expose services that need to be externally available to the cluster and only the services with ports exposed need the ingress network. Containers for backend services with no exposed ports will not be added to the ingress network.
If you do not specify to add an application to a custom network when creating the application, Container Service will create a default network for the application. All the containers of this application are added to the default network. Containers in the network can access each other by using the built-in overlay driver, and can discover services by using the hostname (the same as the container name).
Note: The default network name for your application is
Besides the default network of the application, you can also create a custom network. You can create more complicated network topology and specify the network driver and settings by using the custom network.
After creating a custom network, you can add an application to a custom network when creating the application.
- You can add an application to one or more custom networks to implement inter-service communications.
- You cannot change the custom network for an application after you add the application to the custom network.
- You cannot remove an application from the custom network after you add the application to the custom network.
In the Container Service console, you can:
- Create a custom network
- View network list
- Add an application to a custom network
- View container network
- Delete a custom network
Applications in the same network can access each other by using the container IP address. You can implement inter-service access by adding an application to multiple custom networks.
For more information, see Cross-host interconnected container network.