You need to bind an EIP or configure a NAT Gateway for the container instance and pay additional network fees when the EKSCI needs to connect to a public network, such as deploying a Nginx service, pulling a private image etc. There are two methods for this.
|Method||Description and Use Cases||Cost|
|Elastic IP (EIP) is a fixed public IP address under a certain region and can be purchased and held independently.
Use cases: a single instance or a few instances need to interconnect with a public network, for example, the Nginx service.
|When EIP has not been bound with cloud resource, only IP resource fees are charged. When EIP has been bound with cloud resource, only public network fees are charged. For more information, see Billing for Elastic Public IP.|
|Binding a NAT Gateway||A NAT Gateway is a IP address translation service. It provides secure and high-performance Internet access service for the resources in a VPC.
Use cases: multiple instances under a VPC need to communicate with a public network. For example, multiple instances need to pull images from a third-party image repository.
|NAT Gateway service fees consists two parts: gateway fees (bill on an hourly basis) and network fees (bill by traffic). For more information, see Billing Overview.|
This document describes how to bind an EIP to a container instance, so as to enable the container instance to interconnect with a public network. The steps are as follows:
You need to bind an EIP when creating the container instance.
A container instance supports auto-creating an EIP and binding with it. The attributes are as follows:
You can also select an existing EIP. If you choose this method, you need to create an EIP in advance. If there is no appropriate one, please click Create EIP.