Skip to content

Change max-worker-connections for ingress controller

This document (000021314) is provided subject to the disclaimer at the end of this document.

Environment

RKE1, RKE2 clusters

Situation

Customise the max-worker-connections for the ingress controller deployed in RKE1 or RKE2 downstream clusters (default is 16384).

Resolution

RKE1:

Edit Config of the RKE1 downstream cluster >> Edit as Yaml >> Add the below `addons:` section under `rancher_kubernetes_engine_config`

rancher_kubernetes_engine_config:
  addon_job_timeout: 45
  addons: |-
    ---
    apiVersion: v1
    kind: ConfigMap
    metadata:
      name: ingress-nginx-controller
      namespace: ingress-nginx
    data:
      max-worker-connections: "8192"

RKE2:

Edit config of the RKE2 downstream cluster>> Go to Add-on Config tab >> Additional Manifests section >> Paste the contents below:

---
apiVersion: helm.cattle.io/v1
kind: HelmChartConfig
metadata:
  name: rke2-ingress-nginx
  namespace: kube-system
spec:
  valuesContent: |-
    controller:
      config:
        max-worker-connections: 8192

Similar manifests can be used for upstream RKE1 and RKE2 clusters as well.

Status

Top Issue

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.