vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
Files
remove_swiftapi
doc-exports/docs/cce/umn/cce_10_0500.html
Dong, Qiu Jian f7b9a88535 CCE UMN update -20240625 version 
Reviewed-by: Kovács, Zoltán <zkovacs@t-systems.com>
Co-authored-by: Dong, Qiu Jian <qiujiandong1@huawei.com>
Co-committed-by: Dong, Qiu Jian <qiujiandong1@huawei.com>
2024-09-04 11:43:54 +00:00

2.9 KiB
Raw Permalink Blame History

Private IPv4 Addresses of Load Balancers

Check Items

Check whether the load balancer associated with a Service is allocated with a private IPv4 address.

Solution

Solution 1: Delete the Service that is associated with a load balancer without a private IPv4 address.

Solution 2: Bind a private IP address to the load balancer without a private IPv4 address. The procedure is as follows:

  1. Obtain the load balancer associated with the target Service.

    • Method 1: Obtain the load balancer ID based on the pre-upgrade check log. Go to the ELB console and filter load balancers by load balancer ID.
      elbs (ids: [*****]) without ipv4 private ip, please bind private ip to these elbs and try again
    • Method 2: Log in to the CCE console and click the cluster name to access the cluster console. Then, choose Services & Ingresses in the navigation pane. In the right pane, click the name of the target load balancer to go to the ELB page.

  2. Check whether the load balancer has a private IPv4 address.

  3. Bind a private IP address to the load balancer without a private IPv4 address.

    1. Log in to the CCE console and click the name of the target load balancer.
    2. On the Summary tab, click Bind next to Private IPv4 address.
    3. Configure the subnet and IPv4 address, and click OK.