-
Notifications
You must be signed in to change notification settings - Fork 198
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
Support client IP filtering through loadBalancerSourceRanges in case istioingress #835
Conversation
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, left a suggestion on phrasing
Co-authored-by: Patrik Egyed <[email protected]>
Co-authored-by: Patrik Egyed <[email protected]>
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.
We should sync the CRDs and samples with the new type description through manifest generation.
(Due to the comment change.)
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 adding this!
What's in this PR?
Support client IP filtering through LoadBalancer by allowing users to specify the
loadBalancerSourceRanges
field for the corresponding Kubernetes service when Kafka external listeners useistioingress
as ingress controller.Why?
koperator
doesn't support client IP filtering for Kafka external listeners when those are exposed throughistioingress
ingress controller. Currently this is only supported whenenvoy
is used and ingress controller.Additional context
Checklist