-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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 flag to override GRPC Authority Header #5450
Add flag to override GRPC Authority Header #5450
Conversation
Signed-off-by: Ali Aqel <[email protected]>
bce63f4
to
98dd5f1
Compare
/run-e2e |
@JorTurFer Looks like the FOSSA test failed after I updated to main, known failure? |
I'm going to guess a recent import that merged into main broke this test |
You can ignore it. It was broken due to a package issue, but I've fixed in FOSSA. I've retriggered the check and it should pass now 🤞 |
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!
Co-authored-by: Zbynek Roubalik <[email protected]> Signed-off-by: aliaqel-stripe <[email protected]>
@zroubalik Adopted your comments, let me know how this looks and if we can merge soon so I can consume the CI built Image for this commit |
/run-e2e internal |
* add grpc authority head override command-line flag Signed-off-by: Ali Aqel <[email protected]> Signed-off-by: aliaqel-stripe <[email protected]> Co-authored-by: Zbynek Roubalik <[email protected]> Signed-off-by: Arun Yogesh <[email protected]>
Add a flag to the adapter called
metrics-service-grpc-authority
to allow us to set the Authority Header on the GRPC requests so that it can be a host name that is present in the Certificate SAN issued to the keda-operator pod if the GRPC address differs from that.Validated on my KEDA Deployment and verified this header allows us to use TLS with our service mesh addresses + our CA issued certificates.
Checklist
Fixes #5449
Relates to kedacore/keda-docs#1302