-
Notifications
You must be signed in to change notification settings - Fork 192
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
Automated backport of #3121: Add retry mechanism to CNI interface discovery on kube-proxy #3139
Automated backport of #3121: Add retry mechanism to CNI interface discovery on kube-proxy #3139
Conversation
🤖 Created branch: z_pr3139/yboaron/automated-backport-of-#3121-origin-release-0.17 |
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.
This requires the route agent refactor which was done for 0.18.
We noticed that even though RA pod starts running only after the node is ready, sometimes the kube-proxy handler fails to discover the CNI interface a fter the node is rebooted. This PR adds a retry to CNI discovery. Fixes: submariner-io#3120 Signed-off-by: Yossi Boaron <yboaron@redhat.com>
74474f8
to
1a88e58
Compare
…3121-origin-release-0.17
🤖 Closed branches: [z_pr3139/yboaron/automated-backport-of-#3121-origin-release-0.17] |
submariner-io/submariner#3139 submariner-io/submariner#3162 Signed-off-by: Yossi Boaron <yboaron@redhat.com>
submariner-io/submariner#3139 submariner-io/submariner#3162 Signed-off-by: Yossi Boaron <yboaron@redhat.com>
submariner-io/submariner#3139 submariner-io/submariner#3162 Signed-off-by: Yossi Boaron <yboaron@redhat.com>
submariner-io/submariner#3139 submariner-io/submariner#3162 Signed-off-by: Yossi Boaron <yboaron@redhat.com>
Backport of #3121 on release-0.17.
#3121: Add retry mechanism to CNI interface discovery on kube-proxy
For details on the backport process, see the backport requests page.