Add support for OCP Ingress and standalone OSSMv3 configurations#746
Merged
trepel merged 1 commit intoKuadrant:mainfrom Sep 11, 2025
Merged
Add support for OCP Ingress and standalone OSSMv3 configurations#746trepel merged 1 commit intoKuadrant:mainfrom
trepel merged 1 commit intoKuadrant:mainfrom
Conversation
Signed-off-by: Tomas Repel <trepel@redhat.com>
averevki
approved these changes
Sep 11, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR adds support for both OpenShift Ingress (available in OCP 4.19+) and standalone OSSM v3 configurations in scale tests, making the test compatible with different OSSMv3 deployment scenarios.
Closes #712
Key Changes
openshift-defaultvsistioopenshift.io/gateway-controller/v1vsistio.io/gateway-controllerAdditional Small Changes
httpbin->httpbin-servicein HTTPRoute templates. Reason was that<SERVICE_NAME>_PORTenv var is auto-injected by Kubernetes/OpenShift for every Service in the namespace (in this particular case it isHTTPBIN_PORTand the injected value istcp://<some-ip>:8080) and the httpbin app (fromquay.io/rhn_support_azgabur/httpbin:latest) usesHTTPBIN_PORTenv var for determining the port and it expects numerical value there. This leads toError: 'tcp' is not a valid port number.Verification Steps
Eye review.
Ideal would be to execute both control plane scale test and max gateway listeners test twice - against Kuadrant on OCP v4.19 installed using Openshift Ingress and against Kuadrant on OCP v4.18 or before using standalone OSSMv3. You can just follow the control-plane.md and max-gateway-listeners/README.md files. No need to run the DNS Operator scale test - it is not really used at the moment.