add tests for multitenancy with Service Mesh#2198
add tests for multitenancy with Service Mesh#2198ReToCode wants to merge 9 commits intoopenshift-knative:mainfrom
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ReToCode The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/hold for tests /test 4.10-upstream-e2e-mesh-aws-ocp-410 /test 4.13-upstream-e2e-mesh-aws-ocp-413 |
ReToCode
left a comment
There was a problem hiding this comment.
This PR just adds the tests without Policies. Adding the policies is the next PR.
|
Hm, those make not much sense without the policies 🤣 Going to add those also. |
|
/test 4.10-upstream-e2e-mesh-aws-ocp-410 /test 4.13-upstream-e2e-mesh-aws-ocp-413 |
1 similar comment
|
/test 4.10-upstream-e2e-mesh-aws-ocp-410 /test 4.13-upstream-e2e-mesh-aws-ocp-413 |
There was a problem hiding this comment.
Are these DRs something the chart should own?
There was a problem hiding this comment.
I don't think so, it is just to see if it would work this way. I still would like to go with the mtls: true in SMCP which brings this DR out of the box: https://gist.github.com/ReToCode/132e373bf6a41483e19c65511d3e759a#file-destination-rule-yaml-L34
There was a problem hiding this comment.
We even have that warning on "our" setup: https://kiali.io/docs/features/validations/#kia0401---mesh-wide-destination-rule-enabling-mtls-is-missing. So we definitely should make stuff work with that.
|
/test 4.10-upstream-e2e-mesh-aws-ocp-410 /test 4.13-upstream-e2e-mesh-aws-ocp-413 |
|
Last Eventing failure looks similar to #2183 |
|
I wouldn't do that 9726177 :) |
|
/test 4.10-upstream-e2e-mesh-aws-ocp-410 /test 4.13-upstream-e2e-mesh-aws-ocp-413 |
Not intended to be merged :) I would like to know if it works without the |
|
The reason for not skipping that one anymore is that even after skipping the same error was raised by PingSource for other tests: #2183 (comment), so it's probably an issue with every mesh pod in knative-eventing |
|
PingSource failures are again EOF errors: |
|
/test 4.10-upstream-e2e-mesh-aws-ocp-410 /test 4.13-upstream-e2e-mesh-aws-ocp-413 |
1 similar comment
|
/test 4.10-upstream-e2e-mesh-aws-ocp-410 /test 4.13-upstream-e2e-mesh-aws-ocp-413 |
|
/test 4.10-upstream-e2e-mesh-aws-ocp-410 /test 4.13-upstream-e2e-mesh-aws-ocp-413 /retest |
This reverts commit e00cc73.
|
/test 4.10-upstream-e2e-mesh-aws-ocp-410 /test 4.13-upstream-e2e-mesh-aws-ocp-413 |
|
@ReToCode: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
Closed in favour of: #2199 |
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.