-
Notifications
You must be signed in to change notification settings - Fork 69
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
Tests for Multi Tenancy with Service Mesh #2199
Tests for Multi Tenancy with Service Mesh #2199
Conversation
This reverts commit 90f5d90.
This reverts commit 9726177.
This reverts commit e00cc73.
Signed-off-by: Pierangelo Di Pilato <[email protected]>
Skipping CI for Draft Pull Request. |
/test 4.10-upstream-e2e-mesh-aws-ocp-410 /test 4.13-upstream-e2e-mesh-aws-ocp-413 |
Signed-off-by: Pierangelo Di Pilato <[email protected]>
Previous failure due to
|
/test 4.10-upstream-e2e-mesh-aws-ocp-410 /test 4.13-upstream-e2e-mesh-aws-ocp-413 |
Tests are timing out after 4h |
/test 4.10-upstream-e2e-mesh-aws-ocp-410 /test 4.13-upstream-e2e-mesh-aws-ocp-413 |
Passed on 4.10 /test 4.13-upstream-e2e-mesh-aws-ocp-413 |
/test 4.13-upstream-e2e-mesh-aws-ocp-413 |
APIServer was down:
/test 4.13-upstream-e2e-mesh-aws-ocp-413 |
and there is no pod with name |
/test 4.13-upstream-e2e-mesh-aws-ocp-413 |
2 similar comments
/test 4.13-upstream-e2e-mesh-aws-ocp-413 |
/test 4.13-upstream-e2e-mesh-aws-ocp-413 |
The failures are not related to the authorization policies, generally, those tests are pretty flaky already but one run on 4.10 succeeded https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift-knative_serverless-operator/2199/pull-ci-openshift-knative-serverless-operator-main-4.10-upstream-e2e-mesh-aws-ocp-410/1686049565687418880, so I think we can merge this PR |
eventing tests flaky reason is that tests' resources are not cleaned up, so the cluster is packed of resources, so sometimes pods just get evicted (we use raw pods in tests). This will be hopefully fixed by 1.11 and if we really want we can invest some time into backporting the fixes Refs for commits we need: |
Signed-off-by: Pierangelo Di Pilato <[email protected]>
/test 4.13-upstream-e2e-mesh-aws-ocp-413 |
/test 4.13-upstream-e2e-mesh-aws-ocp-413 |
/test 4.10-upstream-e2e-mesh-aws-ocp-410 |
@pierDipi: The following test failed, say
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm fine with merging this. Mesh tests are already pretty flaky and we have to continue to improve them anyway. It might be good to do it before 1.11 to see where we stand with our mesh changes for the 1.31 release (which is 1.10).
I'll (try) to do the backports and do an additional PR on top here to use mtls: true
, enable the new generation script and see if those back-ports make the tests more stable.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: pierDipi, ReToCode 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 |
Based on #2198
Fixes https://issues.redhat.com/browse/SRVCOM-2522
Proposed Changes
Partial PR with changes from #2126:
-n <namespace>
. This is to reduce duplication of code because the webhook is now used in two namespaces: serving-tests, serverless-tests.TODOs in follow up PRs
make genarated-files
mtls: true
on the SMCP