tencent cloud

Feedback

Accessing Public Network by Binding an EIP

Last updated: 2022-03-31 16:39:56

    Overview

    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
    Binding an EIP 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:

    Directions

    Note

    You need to bind an EIP when creating the container instance.

    1. Log in to the TKE console to go to the container instance page.
    2. Click Create Instance.
    3. Configure the parameters of the container instance based on actual needs. For more information, see Creating a Container Instance. Click Next.
    4. Enable "Binding an EIP". You can use one of the two methods to bind.

      A container instance supports auto-creating an EIP and binding with it. The attributes are as follows:

      • Peak bandwidth, which needs to be customized by you. It will affect billing. Please check the details and select appropriate peak bandwidth based on your needs.
      • Lifecycle, which is consistent with the container instance. When you delete the container instance, the lifecycle is deleted simultaneously.
    5. Click Confirm to complete the process.
    Contact Us

    Contact our sales team or business advisors to help your business.

    Technical Support

    Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

    7x24 Phone Support