A200161411/cloud-container-engine
1
0
Fork 0
forked from docs/cloud-container-engine
Code Pull Requests Activity

Update content

Browse Source
This commit is contained in:
OpenTelekomCloud Proposal Bot 2023-02-14 11:52:57 +00:00
parent 6f89111465
commit e9b73b536f
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
umn/source/networking/ingress/using_elb_ingresses_on_the_console.rst
View File

@ -73,6 +73,7 @@ This section uses an Nginx workload as an example to describe how to add an ELB
- **Forwarding Policies**: When the access address of a request matches the forwarding policy (a forwarding policy consists of a domain name and URL, for example, 10.117.117.117:80/helloworld), the request is forwarded to the corresponding target Service for processing. Click **Add Forwarding Policies** to add multiple forwarding policies. - **Forwarding Policies**: When the access address of a request matches the forwarding policy (a forwarding policy consists of a domain name and URL, for example, 10.117.117.117:80/helloworld), the request is forwarded to the corresponding target Service for processing. Click **Add Forwarding Policies** to add multiple forwarding policies.
- **Domain Name**: actual domain name. Ensure that the domain name has been registered and archived. Once a domain name rule is configured, you must use the domain name for access. - **Domain Name**: actual domain name. Ensure that the domain name has been registered and archived. Once a domain name rule is configured, you must use the domain name for access.
- Rule Matching - Rule Matching
- **Prefix match**: If the URL is set to **/healthz**, the URL that meets the prefix can be accessed. For example, **/healthz/v1** and **/healthz/v2**. - **Prefix match**: If the URL is set to **/healthz**, the URL that meets the prefix can be accessed. For example, **/healthz/v1** and **/healthz/v2**.
@ -88,7 +89,11 @@ This section uses an Nginx workload as an example to describe how to add an ELB
For example, the default access URL of the Nginx application is **/usr/share/nginx/html**. When adding **/test** to the ingress forwarding policy, ensure that your Nginx application contains the same URL, that is, **/usr/share/nginx/html/test**, otherwise, 404 is returned. For example, the default access URL of the Nginx application is **/usr/share/nginx/html**. When adding **/test** to the ingress forwarding policy, ensure that your Nginx application contains the same URL, that is, **/usr/share/nginx/html/test**, otherwise, 404 is returned.
- **Destination Service**: Select an existing Service or create a Service. Services that do not meet search criteria are automatically filtered out. - **Destination Service**: Select an existing Service or create a Service. Services that do not meet search criteria are automatically filtered out.
- **Destination Service Port**: Select the access port of the destination Service.
- .. _cce_10_0251__li118614181492:
**Destination Service Port**: Select the access port of the destination Service.
- Set ELB: - Set ELB:
- **Distribution Policy**: Three algorithms are available: weighted round robin, weighted least connections algorithm, or source IP hash. - **Distribution Policy**: Three algorithms are available: weighted round robin, weighted least connections algorithm, or source IP hash.
@ -100,7 +105,7 @@ This section uses an Nginx workload as an example to describe how to add an ELB
- **Source IP hash**: The source IP address of each request is calculated using the hash algorithm to obtain a unique hash key, and all backend servers are numbered. The generated key allocates the client to a particular server. This enables requests from different clients to be distributed in load balancing mode and ensures that requests from the same client are forwarded to the same server. This algorithm applies to TCP connections without cookies. - **Source IP hash**: The source IP address of each request is calculated using the hash algorithm to obtain a unique hash key, and all backend servers are numbered. The generated key allocates the client to a particular server. This enables requests from different clients to be distributed in load balancing mode and ensures that requests from the same client are forwarded to the same server. This algorithm applies to TCP connections without cookies.
- **Type**: This function is disabled by default. You can select **Load balancer cookie**. - **Type**: This function is disabled by default. You can select **Load balancer cookie**.
- **Health Check**: This function is disabled by default. The health check is for the load balancer. When TCP is selected during the :ref:`port settings <cce_10_0251__li388800117144>`, you can select either TCP or HTTP. By default, the service port (Node Port and container port of the Service) is used for health check. You can also specify another port for health check. After the port is specified, a service port named **cce-healthz** will be added for the Service. - **Health Check**: This function is disabled by default. The health check is for the load balancer. When TCP is selected during the :ref:`port settings <cce_10_0251__li118614181492>`, you can select either TCP or HTTP. By default, the service port (Node Port and container port of the Service) is used for health check. You can also specify another port for health check. After the port is specified, a service port named **cce-healthz** will be added for the Service.
- **Operation**: Click **Delete** to delete the configuration. - **Operation**: Click **Delete** to delete the configuration.