SRVCOM-2356: Use specific labels for Knative gateways to omit conflict

[pierDipi]

This is extracting independent changes from #2183 to help debugging

Proposed Changes

• Use specific labels for Knative gateways to omit conflict

[openshift-ci-robot]

@pierDipi: This pull request references SRVCOM-2356 which is a valid jira issue.

Details

In response to this:

This is extracting independent changes from #2183 to help debugging

Proposed Changes

• Use specific labels for Knative gateways to omit conflict

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-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pierDipi

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [pierDipi]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[pierDipi]

/test ?

[openshift-ci]

@pierDipi: The following commands are available to trigger required jobs:

• /test 4.10-images
• /test 4.10-operator-e2e-aws-ocp-410
• /test 4.10-ui-tests
• /test 4.13-aws-ovn-images
• /test 4.13-azure-images
• /test 4.13-gcp-images
• /test 4.13-hypershift-images
• /test 4.13-images
• /test 4.13-operator-e2e-aws-ocp-413
• /test 4.13-osd-images
• /test 4.13-single-node-images
• /test 4.13-ui-tests
• /test 4.13-vsphere-images
• /test ocp4.14-lp-interop-images
• /test unit-test

The following commands are available to trigger optional jobs:

• /test 4.10-e2e-kitchensink-ocp-410
• /test 4.10-upgrade-kitchensink-ocp-410
• /test 4.10-upgrade-tests-aws-ocp-410
• /test 4.10-upstream-e2e-aws-ocp-410
• /test 4.10-upstream-e2e-kafka-aws-ocp-410
• /test 4.10-upstream-e2e-mesh-aws-ocp-410
• /test 4.13-e2e-kitchensink-ocp-413
• /test 4.13-upgrade-kitchensink-ocp-413
• /test 4.13-upgrade-tests-aws-ocp-413
• /test 4.13-upstream-e2e-aws-ocp-413
• /test 4.13-upstream-e2e-kafka-aws-ocp-413
• /test 4.13-upstream-e2e-mesh-aws-ocp-413

Use /test all to run the following jobs that were automatically triggered:

• pull-ci-openshift-knative-serverless-operator-main-4.10-images
• pull-ci-openshift-knative-serverless-operator-main-4.13-aws-ovn-images
• pull-ci-openshift-knative-serverless-operator-main-4.13-azure-images
• pull-ci-openshift-knative-serverless-operator-main-4.13-gcp-images
• pull-ci-openshift-knative-serverless-operator-main-4.13-hypershift-images
• pull-ci-openshift-knative-serverless-operator-main-4.13-images
• pull-ci-openshift-knative-serverless-operator-main-4.13-operator-e2e-aws-ocp-413
• pull-ci-openshift-knative-serverless-operator-main-4.13-osd-images
• pull-ci-openshift-knative-serverless-operator-main-4.13-single-node-images
• pull-ci-openshift-knative-serverless-operator-main-4.13-upgrade-tests-aws-ocp-413
• pull-ci-openshift-knative-serverless-operator-main-4.13-upstream-e2e-aws-ocp-413
• pull-ci-openshift-knative-serverless-operator-main-4.13-upstream-e2e-kafka-aws-ocp-413
• pull-ci-openshift-knative-serverless-operator-main-4.13-vsphere-images
• pull-ci-openshift-knative-serverless-operator-main-ocp4.14-lp-interop-images
• pull-ci-openshift-knative-serverless-operator-main-unit-test

Details

In response to this:

/test ?

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.

[pierDipi]

/test 4.13-upstream-e2e-mesh-aws-ocp-413

[pierDipi]

/test 4.10-upstream-e2e-mesh-aws-ocp-410

[pierDipi]

@ReToCode will make a PR with more changes extracted from #2183 to make existing mesh tests more stable

[ReToCode]

Here it is: #2196