-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Allow specifying the name of the header for forwarding client certificates #10359
base: main
Are you sure you want to change the base?
Conversation
|
✅ Deploy Preview for kubernetes-ingress-nginx canceled.
|
This issue is currently awaiting triage. If Ingress contributors determines this is a relevant issue, they will accept it by applying the The 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. |
Welcome @tuxillo! |
Hi @tuxillo. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: tuxillo 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 |
@@ -80,6 +81,12 @@ var authTLSAnnotations = parser.Annotation{ | |||
Risk: parser.AnnotationRiskLow, | |||
Documentation: `This annotation defines if the received certificates should be passed or not to the upstream server in the header "ssl-client-cert"`, | |||
}, | |||
annotationAuthTLSPassCertToUpstreamHeader: { | |||
Validator: parser.ValidateNull, |
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 don't ignore the validation, as you are passing a string, you should add what is the possible value
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.
Yeah, I thought so too. Is there any existing example I can follow?
annotationAuthTLSPassCertToUpstreamHeader: { | ||
Validator: parser.ValidateNull, | ||
Scope: parser.AnnotationScopeLocation, | ||
Risk: parser.AnnotationRiskLow, |
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 don't think this is Low, as you are allowing users to:
- Add arbitrary string
- Change the name of a security header
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.
Sure, I don't know the implications of the risk levels. What do you recommend?
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.
IMO we can set it to high level
This is stale, but we won't close it automatically, just bare in mind the maintainers may be busy with other tasks and will reach your issue ASAP. If you have any question or request to prioritize this, please reach |
Yes please, don't close it :) |
It wont :) I just didn't had time to reach it, maybe on weekend (no promises, but will try!) |
@tuxillo I cant remember if we have an e2e test for authttls, but if we do do you mind adding a case for this annotation? Thanks! |
PR needs rebase. 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-sigs/prow repository. |
What this PR does / why we need it:
Try to address #3511 .
Types of changes
Which issue/s this PR fixes
How Has This Been Tested?
Just did a
make build
:)Checklist: