Configuring Timeout for a LoadBalancer Ingress

Notes and Constraints

• The following table lists the scenarios where timeout can be configured for a Service.

  Timeout Type	Load Balancer Type	Supported Cluster Version
  Idle Timeout	Dedicated	v1.19: v1.19.16-r30 or later v1.21: v1.21.10-r10 or later v1.23: v1.23.8-r10 or later v1.25: v1.25.3-r10 or later Other clusters of later versions
  Request Timeout	Dedicated
  Response Timeout	Dedicated
  Idle Timeout	Shared	v1.23: v1.23.13-r0 or later v1.25: v1.25.8-r0 or later v1.27: v1.27.5-r0 or later v1.28: v1.28.3-r0 or later Other clusters of later versions
  Request Timeout	Shared
  Response Timeout	Shared

• If you delete the timeout configuration during an ingress update, the timeout configuration on the existing listeners will be retained.

Using the CCE Console

1. Log in to the CCE console and click the cluster name to access the cluster console.
2. In the navigation pane, choose Services & Ingresses. Click the Ingresses tab and click Create Ingress in the upper right corner.
3. Configure ingress parameters. In this example, only mandatory parameters are listed. For details about how to configure other parameters, see Creating a LoadBalancer Ingress on the Console.
   • Name: can be the same as the workload name.
   • Load Balancer: Select a load balancer type and creation mode.
     • A load balancer can be dedicated or shared.
     • This section uses an existing load balancer as an example. For details about the parameters for automatically creating a load balancer, see load balancers.
   • Listener
     • External Protocol: HTTP and HTTPS are available. This section uses HTTP as an example.
     • External Port: port number that is open to the ELB service address. The port number is configurable.
     • Advanced Options

       Configuration	Description
       Idle Timeout	Timeout for an idle client connection. If there are no requests reaching the load balancer during the timeout duration, the load balancer will disconnect the connection from the client and establish a new connection when there is a new request.
       Request Timeout	Timeout for waiting for a request from a client. There are two cases: If the client fails to send a request header to the load balancer during the timeout duration, the request will be interrupted. If the interval between two consecutive request bodies reaching the load balancer is greater than the timeout duration, the connection will be disconnected.
       Response Timeout	Timeout for waiting for a response from a backend server. After a request is forwarded to the backend server, if the backend server does not respond during the timeout duration, the load balancer will stop waiting and return HTTP 504 Gateway Timeout.

   • Forwarding Policy: Specify a domain name matching rule and the target Service to be accessed. 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 will be forwarded to the target Service for processing.

4. Click OK.

Using kubectl

An ingress configuration example is as follows:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: test
  namespace: default
  annotations:
    kubernetes.io/elb.port: '80'
    kubernetes.io/elb.id: <your_elb_id>    # In this example, an existing dedicated load balancer is used. Replace its ID with the ID of your dedicated load balancer.
    kubernetes.io/elb.class: performance
    kubernetes.io/elb.keepalive_timeout: '300'  # Timeout setting for client connections
    kubernetes.io/elb.client_timeout: '60'      # Timeout duration for waiting for a request from a client
    kubernetes.io/elb.member_timeout: '60'      # Timeout for waiting for a response from a backend server
spec:
  rules:
    - host: ''
      http:
        paths:
          - path: /
            backend:
              service:
                name: test
                port:
                  number: 80
            property:
              ingress.beta.kubernetes.io/url-match-mode: STARTS_WITH
            pathType: ImplementationSpecific
  ingressClassName: cce