Help Center/ Cloud Container Instance/ Developer Guide/ Managing Network Access Through Service and Ingress/ Network Access Scenarios
Updated on 2023-02-07 GMT+08:00
View PDF
Share

Network Access Scenarios

The previous two sections describe how to access pods through Services and ingresses. This section describes scenarios of accessing pods in CCI, as shown in Figure 1. In each scenario, Services and ingresses can be used to solve access problems.

  • Intra-namespace access: You only need to create a Service. A workload can be accessed from other workloads in the same namespace by using Service name:Service port.
  • Intra-VPC access: A workload can be accessed from other workloads in the same VPC by using the IP address of a Service or the IP address of the private network load balancer bound to an ingress.
  • Inter-VPC access: You can create a VPC peering connection to connect two VPCs. A workload is accessible to workloads in the other VPC by using the IP address of a Service or the IP address of the private network load balancer.
  • Access to a workload from the public network: A workload can be accessed from the outside of Huawei Cloud by using the IP address of the public network load balancer bound to an ingress.
  • Access to the public network from a workload: You can configure source network address translation (SNAT) rules in NAT Gateway, so that containers can access the public network. For details, see Accessing Public Networks from a Container.
Figure 1 Network access diagram