-
Notifications
You must be signed in to change notification settings - Fork 689
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
Add support for "projectcontour.io/tls-cert-namespace" annotation #4271
Add support for "projectcontour.io/tls-cert-namespace" annotation #4271
Conversation
Codecov Report
@@ Coverage Diff @@
## main #4271 +/- ##
==========================================
+ Coverage 77.74% 77.82% +0.08%
==========================================
Files 112 112
Lines 10014 10020 +6
==========================================
+ Hits 7785 7798 +13
+ Misses 2046 2040 -6
+ Partials 183 182 -1
|
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.
Thanks for the PR @pablo-ruth! I think this is a reasonable approach here for giving folks an option to keep using this functionality when moving to Ingress v1, but others with more of the backstory here can chime in as well.
Assuming we go forward with this, I'd also like to see some test cases added to:
- internal/dag/builder_test.go
- internal/featuretests/v3/tlscertificatedelegation_test.go
And some docs updates:
0cc4420
to
865a179
Compare
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 think one unit test to fix, included an Ingress with namespace in the secret name
Looks like a good solution to me. However we went "all-in" with GatewayAPI together with contour in order to be able to update to k8s 1.22. Nevertheless I'd like to see this merged too 👍🏻 |
Signed-off-by: Pablo Ruth <contact@pablo-ruth.fr> Signed-off-by: Pablo RUTH <contact@pablo-ruth.fr>
Signed-off-by: Pablo RUTH <contact@pablo-ruth.fr>
Signed-off-by: Pablo RUTH <contact@pablo-ruth.fr>
Signed-off-by: Pablo RUTH <contact@pablo-ruth.fr>
Co-authored-by: Sunjay Bhatia <5337253+sunjayBhatia@users.noreply.github.com> Signed-off-by: Pablo RUTH <contact@pablo-ruth.fr>
Signed-off-by: Pablo RUTH <contact@pablo-ruth.fr>
e086d21
to
73612c3
Compare
Thanks @sunjayBhatia for the fix on the test, I merged it. As discussed @skriss I added tests on both test files and updated the docs. |
@pablo-ruth thanks for those updates, they all LGTM. The last thing I see to do here is to add a changelog file, |
Signed-off-by: Pablo RUTH <contact@pablo-ruth.fr>
Thanks again @pablo-ruth for contributing this change! |
Thanks for your guidance ! |
…tation Follow-up to projectcontour#4271, updates the ingress.md page to also describe the new annotation. Closes projectcontour#4282. Signed-off-by: Steve Kriss <krisss@vmware.com>
Follow-up to projectcontour#4271, updates the ingress.md page to also describe the new annotation. Closes projectcontour#4282. Signed-off-by: Steve Kriss <krisss@vmware.com>
Hello,
Following the issue raised in #3544 we are maintaining an internal fork of Contour to be able to use TLS Delegation with Ingress v1. After a discussion with our Tanzu Solution Egineer @lzetea we decided that it could be interesting to propose our changes upstream.
We described our context here to @xaleeks and it seems to be similar to @ghouscht here.
@youngnick said that using an annotation could be the only way to go so I used this approach. I tried to keep the code simple and the change very small. It's backward compatible with "namespace/secret" syntax because the annotation is used only if namespace is blank. It doesn't cover the case where you have multiple TLS secrets from different namespaces.