-
Notifications
You must be signed in to change notification settings - Fork 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
pkg/redirectpolicy: Make code robust against incorrect policy configu… #16216
pkg/redirectpolicy: Make code robust against incorrect policy configu… #16216
Conversation
@aditighag hey, what's the status of this PR? I've been waiting for it to be marked ready for review before having a look. |
test-only --focus="K8sServicesTest.* LRP" --kernel_version="net-next" |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
4cbaf5f
to
70d510a
Compare
test-only --focus="K8sLRPTests" --kernel_version="net-next" Rebased the PR. |
Focused tests relevant to the code changes (LRP tests) have passed. |
Reviews are in and focused LRP tests have passed - https://jenkins.cilium.io/job/Cilium-PR-Tests-Kernel-Focus/293/. Based on the out-of-band comment from Jussi, I've added a comment in the commit description and the code. No need to re-run the test. Edit : checkpath warning can be ignored -
|
…rations If an incorrect service name is specified in an LRP, we need to guard against this case when service IP can't be retrieved. Also, when a valid LRP is applied before the service it selects, service information won't be available in the manager callback to add an LRP. The LRP will be applied when the service callback is later received by the manager. Signed-off-by: Aditi Ghag <aditi@cilium.io>
43ee72c
to
ce0d7af
Compare
See commit message.
Fixes: #16204
Release note