-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Remove deprecated call to DialContext in Hubble #34241
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
Remove deprecated call to DialContext in Hubble #34241
Conversation
Hi, |
/test |
825654f
to
81df16b
Compare
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 overall.
My only nitpick is that the --timeout
flag is now unused, which I think is fine as I think previously the timeout didn't quite work as expected anyways. The most common actual dial errors, because the server was not (yet) running, instantly failed anyways because of grpcOptionFailOnNonTempDialError
.
So IMO this is fine, but we should mark it as deprecated (using ServerFlags.MarkDeprecated
)
CC @kaworu (Maybe you have a different opinion. It will change the behavior of the CLI slightly)
Alternatively we could make |
Hi @chancez, |
By removing |
81df16b
to
0357a39
Compare
Looking into it
If correct, then I don't think aliasing So I would prefer removing |
/test |
0357a39
to
96b5176
Compare
/test |
96b5176
to
9a3d23a
Compare
/test |
9a3d23a
to
d3d6e63
Compare
/test |
Related:cilium#32274 Update hubble/cmd/common/conn/conn.go Co-authored-by: Alexandre Perrin <alex@kaworu.ch> Signed-off-by: davchos <dchosrova@gmail.com>
d3d6e63
to
b44c4a7
Compare
/test |
Remove deprecated call to DialContext in Hubble
Related:#32274, #33065
Signed-off-by: David Chosrova dchosrova@gmail.com