Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
On this page

Show all

Help Center/ Cloud Container Engine/ FAQs/ Networking/ Network Configuration/ How Do I Set the Port When Configuring the Workload Access Mode on CCE?

How Do I Set the Port When Configuring the Workload Access Mode on CCE?

Updated on 2024-09-04 GMT+08:00

Workloads in a CCE cluster can access each other and can be accessed from the Internet.

  • Workloads can access each other through ClusterIP (the virtual IP address of a cluster) and NodePort (a node IP address).
    Table 1 Internal access description

    Access Type

    Description

    Guide

    ClusterIP (the virtual IP address of a cluster)

    Used for mutual access between workloads in a cluster. For example, if a backend workload needs to communicate with a frontend workload, use this access type.

    When this access type is selected, a cluster IP address is automatically allocated.

    • Container port: the port on a container on which the workload listens. The container port varies with the service. Typically, a container port is specified in the container image.
    • Service port: the port configured for the workload after the workload was associated with a Service. Enter an integer from 1 to 65535. Workloads in a cluster can access each other through {Cluster IP}:{Access port number}.

    NodePort (through a node IP address)

    The workload can be accessed through {Node IP address}:{Node port number}. If an EIP is bound to the node, the workload can be accessed from the external networks.

    • Container port: the port on a container on which the workload listens. The container port varies with the service. Typically, a container port is specified in the container image.

    • Service port: the port configured for the workload after the workload was associated with a Service. Enter an integer from 1 to 65535.
    • Node port: the port on the node to which the container is mapped. After the configuration is complete, an actual port is open on all nodes in the project to which the user belongs. The workload can be accessed through {Node IP}:{Node port number}.

      If there are no special requirements, select Automatically generated so that the system automatically assigns an access port. If you select Specified port, enter an integer ranging from 30000 to 32767 and ensure that the value is unique in the cluster.

  • A workload can be accessed from the Internet through NodePort (using an EIP), LoadBalancer, or DNAT.
    Table 2 External access description

    Access Type

    Description

    Guide

    NodePort (using an EIP)

    If the node where the workload runs is bound with an EIP, the workload can be accessed through {Node EIP}:{Node port number}. The workload can then be accessed from the Internet.

    • Container port: the port on a container on which the workload listens. The container port varies with the service. Typically, a container port is specified in the container image.

    • Service port: the port configured for the workload after the workload was associated with a Service. Enter an integer from 1 to 65535.
    • Node port: the port on the node to which the container is mapped. After the configuration is complete, an actual port is open on all nodes in the project to which the user belongs. The workload can be accessed through {Node IP}:{Node port number}.

      If there are no special requirements, select Automatically generated so that the system automatically assigns an access port. If you select Specified port, enter an integer ranging from 30000 to 32767 and ensure that the value is unique in the cluster.

    LoadBalancer

    ELB automatically distributes access traffic to multiple nodes to balance their service load. It supports higher levels of fault tolerance for workloads and expands workload service capabilities.

    You need to create an ELB instance in advance and select ELB as the CCE access type.

    • Container port: the port on a container on which the workload listens. The container port varies with the service. Typically, a container port is specified in the container image.
    • Service port: the port registered with a load balancer. Enter an integer ranging from 1 to 65535. External users can use {Virtual IP address of the load balancer }:{Service port number} to access the workload.

    DNAT

    NAT gateways provide network address translation (NAT) for cloud servers so that multiple cloud servers can share an EIP.

    You need to buy a public NAT gateway in advance.

    • Container port: the port on a container on which the workload listens. The container port varies with the service. Typically, a container port is specified in the container image.
    • Service port: the port registered on your NAT gateway. Enter an integer ranging from 1 to 65535. The system automatically creates DNAT rules. External users can access the workload through {EIP of the NAT gateway}:{Service port number}.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback