-
Notifications
You must be signed in to change notification settings - Fork 19
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
fix: reconcile gateway client's node port #368
fix: reconcile gateway client's node port #368
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 👍
Sure @kon3m, will review it and update you soon. |
@narmidm a lot of e2e tests seem to fail after the recent update made to the pipeline. |
We've identified the root cause of the end-to-end failure; it was due to the last release. Please allow me half an hour to release a new image for automation, after which I will rerun and verify your PR. Apologies for the delayed response. |
@kon3m We have added a small fix for the PR pipeline failure. Please re-sync. |
Signed-off-by: kon3m <[email protected]>
4301fec
to
5c9b367
Compare
@mridulgain @narmidm i have just updated it, can you please trigger the e2e pipeline? |
Description
Fixes #309
How Has This Been Tested?
Tested it manually using two single node kind clusters.
Checklist:
go fmt
Does this PR introduce a breaking change?