Skip to content
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

[release/0.8] Backport networking commits #2173

Conversation

princepereira
Copy link
Contributor

These are direct ports of the following commits without any additional changes from main to release/0.12 :

c79a631 : #2106 ---> direct cherry-pick

8beabac : #2139 ---> This commit had merge conflicts that were fixed.

0f7d8de : #2085 ---> This commit had merge conflicts that were fixed.

@princepereira princepereira requested a review from a team as a code owner June 14, 2024 14:21
@princepereira
Copy link
Contributor Author

/cc @kiashok
/cc @debj1t

@kiashok
Copy link
Contributor

kiashok commented Jun 14, 2024

@princepereira are the lint errors related to your changes?

@princepereira
Copy link
Contributor Author

@princepereira are the lint errors related to your changes?

Doesn't look like part of my changes. But let me recheck and get back.

@princepereira princepereira force-pushed the user/ppereira/modifyLoadbalancerBackport0.8 branch 2 times, most recently from e751fd0 to eb1159c Compare June 19, 2024 04:49
@princepereira princepereira force-pushed the user/ppereira/modifyLoadbalancerBackport0.8 branch from eb1159c to 467f63f Compare June 19, 2024 04:56
@princepereira
Copy link
Contributor Author

princepereira commented Jun 19, 2024

@princepereira are the lint errors related to your changes?

@kiashok , issue was with some buggy version of golang-lint. I have updated the golang-lint version and now it's working.

@kiashok kiashok merged commit 429b0d2 into microsoft:release/0.8 Jun 19, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants