-
Notifications
You must be signed in to change notification settings - Fork 351
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
feat: support sni based tls route #1051
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1051 +/- ##
==========================================
+ Coverage 40.62% 41.42% +0.80%
==========================================
Files 75 82 +7
Lines 7006 7234 +228
==========================================
+ Hits 2846 2997 +151
- Misses 3847 3891 +44
- Partials 313 346 +33
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
@mangoGoForward Please make the CI pass, thanks! See https://github.com/apache/apisix-ingress-controller/runs/6623221714?check_suite_focus=true. |
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.
Please also add some e2e test cases to cover the SNI route feature.
I got some |
Thanks, I will do. |
9c5ad20
to
9180875
Compare
Hi @tokers How can I generate a |
9180875
to
ed12a07
Compare
@mangoGoForward Unfortunately, current CRDs are manually maintained. We have #515 to track it. |
ed12a07
to
b2dd8b1
Compare
Signed-off-by: mango <xu.weiKyrie@foxmail.com>
b2dd8b1
to
d09d14c
Compare
Please merge master latest code, and resolve conflicts. Thanks |
Signed-off-by: mango <xu.weiKyrie@foxmail.com> # Conflicts: # test/e2e/suite-features/global_rule.go # test/e2e/suite-ingress/ingress.go
OK. I will solve it later. |
Signed-off-by: mango <xu.weiKyrie@foxmail.com>
@mangoGoForward Please make the CI passed, it has some failures. Thanks! |
OK, I haven't found the the target of this error, it may takes a while to resolve. |
@mangoGoForward hi, thanks for your contribution, we plan to enter v1.5 release window. I have a few suggestions for this PR
|
Hi, do you have time to pick up this one? Thanks |
Signed-off-by: mango <xu.weiKyrie@foxmail.com> # Conflicts: # pkg/providers/apisix/translation/apisix_route.go # test/e2e/suite-ingress/suite-ingress-resource/stream.go
Yes, the file conflicts solved |
@mangoGoForward Thanks for your active contribution!
|
Signed-off-by: mango <xu.weiKyrie@foxmail.com>
Signed-off-by: mango <xu.weiKyrie@foxmail.com>
LGTM ! could you please add e2e test cases to covet this one? thanks! |
Sure, but have no time to deal with it recently, I will improve it as soon as possible |
Now that we're in the v1.6 development cycle, do you have time to add e2e test cases to covet this one? Thanks! |
Sorry reply to late, will be completed this week |
Thanks! @mangoGoForward |
Signed-off-by: mango <xu.weiKyrie@foxmail.com>
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.
LGTM
But I think a more complete case can be added in e2e.
Create a certificate pair and use it for proxying.
But we can do it in a follow-up PR #1438 @mangoGoForward |
Thanks, it absolutely need more test cases to cover it. I need to study how the TLS route with SNI works and how to test it, I am so poor about knowledge in this area. |
Don't worry, you can continue if you are interested. Otherwise see if others are interested. |
Signed-off-by: mango xu.weiKyrie@foxmail.com
Type of change:
What this PR does / why we need it:
Please see #547
Pre-submission checklist: