-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Implement e2e test for internal encryption #13536
Conversation
Skipping CI for Draft Pull Request. |
Codecov ReportBase: 86.16% // Head: 86.24% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #13536 +/- ##
==========================================
+ Coverage 86.16% 86.24% +0.07%
==========================================
Files 197 197
Lines 14790 14783 -7
==========================================
+ Hits 12744 12749 +5
+ Misses 1743 1733 -10
+ Partials 303 301 -2
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
a22a75e
to
a7a1cdd
Compare
a7a1cdd
to
1f6e0f2
Compare
/test contour-internal-encryption |
Hi! Looking at the "kourier" variant, the internal TLS is configured in e2e-common.sh here based on the ENABLE_TLS flag. This flag is enabled via github action here. This way all the E2E tests in Serving run with internal TLS enabled for kourier. The github action run can be seen above as |
hi @mgencur thanks for sharing that! I think that makes sense, I was worried my approach wasn't going to be able to test very much anyway. I will look into it |
052b346
to
a1a7132
Compare
okay, I've tried out @mgencur 's suggestions. They're all failing currently, but I'm thinking that is because it is using Contour 1.23.x. The net-contour internal-encryption compatibility relies on some changes coming in Contour 1.24. That should be out soon. In the mean-time, I will try bringing in the release candidate to my fork of net-contour and test this PR out with that. |
b1afd86
to
e5c1202
Compare
e5c1202
to
7cf7589
Compare
7cf7589
to
8a1bed5
Compare
As an update, looks like the only failing tests using the new Contour 1.24 are the DomainMapping api tests. I think I see what is going on there, so I started a new issue: #13659 EDIT: moved the issue to net-contour repo: knative-extensions/net-contour#862 |
Contour 1.24.0 is available, hopefully that can get pulled into net-contour soon. UPDATE: I'm drafting a PR to test it out here |
8a1bed5
to
f172b1f
Compare
This PR (knative-extensions/net-contour#860) should make the failing contour-tls api tests pass here |
* can achieve more test coverage by modifying workflow and reusing existing e2e tests
f172b1f
to
541d155
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: KauzClay The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
I just rebased with main, so serving should have my changes for knative-extensions/net-contour#860 in 51ed9ad. Hopefully the tests all pass now 🤞 |
looks like those changes didn't work, trying again with knative-extensions/net-contour#878 |
This Pull Request is stale because it has been open for 90 days with |
closing in favor of #14092 |
Fixes #
Proposed Changes
Release Note
N/A