Configuring timeouts for management endpoints

Adjust the timeout settings for management endpoints by updating the CR.

About this task

On large deployments, or with large API usage, you might encounter timeout issues when deployed with the default timeout setting of 30 seconds. To avoid timeout issues, increase the setting for the management endpoints used in routing.

You do not have to set these values on initial installation. You can set them or change them after installation and reapply the CR YAML files.

Procedure

Edit the CR to set the timeout to 240 seconds.

The instructions for editing depend on whether you install API Connect using subsystem CRs or a single top-level CR:

  • If you are installing API Connect using subsystem CRs, edit management_CR.yaml:
    
      cloudManagerEndpoint:
        annotations:
          haproxy.router.openshift.io/timeout: 240s
        hosts: 
        - name: admin.example.com
          secretName: cm-endpoint
      apiManagerEndpoint:
        annotations:
          haproxy.router.openshift.io/timeout: 240s
        hosts: 
        - name: manager.example.com
          secretName: apim-endpoint
      platformAPIEndpoint:
        annotations:
          haproxy.router.openshift.io/timeout: 240s
        hosts: 
        - name: api.example.com
          secretName: api-endpoint
      consumerAPIEndpoint:
        annotations:
          haproxy.router.openshift.io/timeout: 240s
        hosts: 
        - name: consumer.example.com
          secretName: consumer-endpoint
  • If you are installing API Connect using a top-level CR, the management subsystem settings are embedded in the top-level APIConnectCluster CR. Edit the endpoint settings under spec:management: as follows:
    apiVersion: apiconnect.ibm.com/v1beta1
    kind: APIConnectCluster
    metadata:
      labels:
        app.kubernetes.io/instance: apiconnect
        app.kubernetes.io/managed-by: ibm-apiconnect
        app.kubernetes.io/name: apiconnect-minimum
      name: <name_of_your_instance> 
      namespace: ${NAMESPACE} 
    spec:
    ...
      management:
        cloudManagerEndpoint:
          annotations:
            haproxy.router.openshift.io/timeout: 240s
          hosts: 
          - name: admin.example.com
            secretName: cm-endpoint
        apiManagerEndpoint:
          annotations:
            haproxy.router.openshift.io/timeout: 240s
          hosts: 
          - name: manager.example.com
            secretName: apim-endpoint
        platformAPIEndpoint:
          annotations:
            haproxy.router.openshift.io/timeout: 240s
          hosts: 
          - name: api.example.com
            secretName: api-endpoint
        consumerAPIEndpoint:
          annotations:
            haproxy.router.openshift.io/timeout: 240s
          hosts: 
          - name: consumer.example.com
            secretName: consumer-endpoint
    ...