Run upstream e2e test with net-istio#1014
Run upstream e2e test with net-istio#1014openshift-merge-robot merged 2 commits intoopenshift-knative:mainfrom nak3:add-net-istio-test
Conversation
|
@nak3: GitHub didn't allow me to request PR reviews from the following users: nak3. Note that only openshift-knative members and repo collaborators can review this PR, and authors cannot review their own PRs. DetailsIn 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. |
|
/retest |
|
/test 4.7-upstream-e2e-aws-ocp-47 |
|
domainmapping test hits this issue knative/serving@26c93b9 |
|
|
|
grpc_test.go must be removed. It hangs and got timeout. |
|
Hmm... it should be fixed by #1036 |
|
The original CR |
|
The test passed. Now trying to remove |
|
/retest New failure with |
|
It will be improved by knative/serving@9054d8b 🤔 |
|
/retest
|
|
/retest Test passed once. One more time. |
|
Serving 0.22 didn't have h2c issue but 0.23 got the issue log: I experienced it in openshift/knative-serving#751 but still not sure why only serving 0.23 happens this problem. |
|
/retest TestRouteCreation failed. (It is the first time to fail it.) |
|
Only two HA tests failed. |
|
Umm... TestControllerHA still failed. openshift/knative-serving#836 might not be applied. |
|
/retest |
|
/cc @markusthoemmes @mgencur @maschmid This is ready for review. Could you please take a look? |
|
@nak3 should we run downstream tests with this setup as well? Is this coming next? I would like to test metrics (ideally tracing too). |
|
Yes, I am going to add the mesh test for downstream with follow up PR. (Because it messes up script and hard to review I guess |
Makefile
Outdated
| # This is to run with FULL_MESH to verify the PR. Remove this and use "test-upstream-e2e-mesh". | ||
| FULL_MESH=true TEST_KNATIVE_KAFKA=false TEST_KNATIVE_E2E=true TEST_KNATIVE_UPGRADE=false ./test/upstream-e2e-tests.sh | ||
| # INSTALL_KAFKA=true TEST_KNATIVE_KAFKA=true TEST_KNATIVE_E2E=true TEST_KNATIVE_UPGRADE=false ./test/upstream-e2e-tests.sh |
There was a problem hiding this comment.
Should this go away before a merge?
There was a problem hiding this comment.
Yes, correct. This is a temporary as pre-submit PR always run test-upstream-e2e-no-upgrade. I will revert it and trigger job against test-upstream-e2e-mesh.
| # TODO: SRVKS-211: Can not run grpc and http2 tests. | ||
| rm ./test/e2e/grpc_test.go | ||
| rm ./test/e2e/http2_test.go | ||
| # Remove h2c test | ||
| sed -ie '46,50d' ./test/conformance/runtime/protocol_test.go |
There was a problem hiding this comment.
This means that we'll have to document gRPC/HTTP2 not working for mesh for now, right?
There was a problem hiding this comment.
Yes, I will open the JIRA.
| config: | ||
| observability: | ||
| metrics.backend-destination: "none" |
There was a problem hiding this comment.
Is this required? Don't we do that "automatically"?
There was a problem hiding this comment.
Umm... we have the default as "prometheus"
so I think we need to override it with
none. Sorry if I misunderstood the meaning of "automatically".
There was a problem hiding this comment.
ahhhh we explicitly set it. Nevermind then, I was thinking in our Golang code, where we default to none currently, if istio is enabled.
| - name: domain-mapping | ||
| replicas: 2 |
There was a problem hiding this comment.
Why do we need this? Don't we also need that in "usual" setups?
There was a problem hiding this comment.
Yes, we have the replicas: 2 in "usual" setups.
But the
spec.deployments is an array. So when we patch the annotation (inject and rewriteAppHTTPProbers) to spec.deployments for activator and autoscaler, domain-mapping's replicas: 2 is dropped 😓
There was a problem hiding this comment.
Gotcha, makes sense!
| # Use x509ignoreCN=0. | ||
| # This should not be necesssary if we could ceate certs with SAN. However, openssl command in the CI | ||
| # seems old version and so it does not have "-addext" option to add SAN. | ||
| export GODEBUG="x509ignoreCN=0" |
There was a problem hiding this comment.
We should be able to fix that. Can we update the openssl command in https://github.com/openshift-knative/serverless-operator/blob/main/openshift/ci-operator/build-image/Dockerfile?
There was a problem hiding this comment.
I tried but the base image of registry.ci.openshift.org/openshift/release:golang-1.15 is CentOS 7 and the latest openssl command was still 1.10.
$ docker run build-image rpm -qf `which openssl`
openssl-1.0.2k-21.el7_9.x86_64
markusthoemmes
left a comment
There was a problem hiding this comment.
/lgtm
/approve
/hold
Please revert the "old" make target and then we're good to go here :)
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: markusthoemmes, nak3 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 cancel |
/cc