New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[release-4.14] OCPBUGS-21898: test/e2e: Add test case for 2000000 maxConnections #984
[release-4.14] OCPBUGS-21898: test/e2e: Add test case for 2000000 maxConnections #984
Conversation
This commit adds a test case to verify that the maxConnections setting can be configured with the absolute upper limit of 2000000, as defined by the API % oc explain ingresscontroller.spec.tuningOptions.maxConnections KIND: IngressController VERSION: operator.openshift.io/v1 FIELD: maxConnections <integer> DESCRIPTION: maxConnections defines the maximum number of simultaneous connections that can be established per HAProxy process. Increasing this value allows each ingress controller pod to handle more connections but at the cost of additional system resources being consumed. Permitted values are: empty, 0, -1, and the range 2000-2000000. This change requires openshift/router#527. Fixes: https://issues.redhat.com/browse/OCPBUGS-21803.
@openshift-cherrypick-robot: Detected clone of Jira Issue OCPBUGS-21803 with correct target version. Will retitle the PR to link to the clone. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-21898, which is valid. The bug has been moved to the POST state. 6 validation(s) were run on this bug
Requesting review from QA contact: The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/assign @Miciah |
/approve |
Note that e2e-*-operator jobs are expected to fail until openshift/router#528 merges. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Miciah The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
Assuming this clears CI, the PR is missing |
/label cherry-pick-approved |
@knobunc: Can not set label cherry-pick-approved: Must be member in one of these teams: [] In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@openshift-cherrypick-robot: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
@openshift-cherrypick-robot: Jira Issue OCPBUGS-21898: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-21898 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Fix included in accepted release 4.14.0-0.nightly-2023-10-22-172722 |
This is an automated cherry-pick of #983
/assign frobware