-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Remove deprecated call to DialContext in Hubble server #34261
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 server #34261
Conversation
Hi @tklauser, I have 2 questions, before pushing this PR, I have used make kind / make kind-image-fast / make kind-install-cilium-fast I have sent a commit to remove the unused import, the check is still failing, so is it best now to close this PR and re submit a new one. Thanks in advance for your help. David |
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.
Hi David thanks for the contribution!
For you're two questions:
-
The reason why
make kind-image-fast
didn't catch the issue is because it doesn't actually build the relay image. So it wasn't actually compiling your code changes. Sadly, the Hubble Relay development isn't quite a streamlined, it's not even enabled by default when you usemake kind / make kind-image-fast / make kind-install-cilium-fast
.To actually run your Relay changes you need to build the image yourself and enable relay by running the following after you created the kind cluster
DOCKER_IMAGE_TAG=local make docker-hubble-relay-image
kind load docker-image quay.io/cilium/hubble-relay:local
cat << EOF > contrib/testing/kind-custom.yaml
hubble:
relay:
enabled: true
image:
override: quay.io/cilium/hubble-relay:local
pullPolicy: Never
EOF
make kind-install-cilium-fast
- The reason CI is still failing is that we actually require that every commit builds successfully, not just the last commit. You can just squash your 4 commits into a single commit and CI should be happy again.
On a first look your changes look good, but I think we can actually get rid of the DialTimeout
and the related option and flag as it doesn't do anything anymore (and then even remove it from the helm chart)
I still want take a closer look how this will impact the peer manager though, just to be sure we don't break anything unexpectedly by removing this timeout. But I won't get to that today, so I'll give you another review on Monday.
fcca79b
to
3b1f5ba
Compare
Alright, I took another look and I think removing this timeout is fine. It won't change anything for the connection to the peers and connection retries to the peer service will have a slightly different timing, because we don't have the same timeout when dialing on the first call, but that should be fine. So let's just remove the unused |
Hi Fabian, I will remove the timeout, not available today I do it tomorrow. Have a good day. David |
a9119fa
to
c7d591b
Compare
No idea why this test is failing (Conformance K8s Upstream Network / Installation and Conformance Test (ipv4)), the cilium installation looks ok, Hubble relay not enabled. |
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.
One final nitpick, otherwise this LGTM
And the CI failure seems like an unrelated flake.
358f67b
to
9af47e9
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 🚀
/test |
@glrf, I have checked the failed checks, don't "think" (hope) it is related to the changes I have done. David |
Sadly, that one does seem related: https://github.com/cilium/cilium/actions/runs/10382885529/job/28746842560 We introduce a small issue during startup. When the DNS server is not (yet) available, IMO for now it would be fine to just drop the severity of that log message from Longer term we might want to take a closer look at the Peer service connection and how we handle retries and make something smarter than just tearing down everything and retrying in 30 seconds. But I think that's out of scope of this PR and that's something I wanted to do for a while now anyways. |
Thanks for the explanation, I'll change the log level. |
Commit 84cf6c6 does not match "(?m)^Signed-off-by:". Please follow instructions provided in https://docs.cilium.io/en/stable/contributing/development/contributing_guide/#developer-s-certificate-of-origin |
Hi, After running locally the "make -C bpf checkpatch" I get errors, "Warning: WARNING:BAD_SIGN_OFF: Duplicate signature". Maybe it is better to close this PR and re create a clean one ? David |
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.
I found a non-blocking nit, but LGTM. Thank you!
Commit 84cf6c6 does not match "(?m)^Signed-off-by:". Please follow instructions provided in https://docs.cilium.io/en/stable/contributing/development/contributing_guide/#developer-s-certificate-of-origin |
That shouldn't be necessary. I think the issue is related to the merge commits from merging main into this branch. At least the last merge commit isn't signed off which is definitely an issue and I think our tooling in general assumes that we rebase instead of merge to update branches. Could you please drop your two merge commits and then rebase on main? That should fix the issue. |
85818bb
to
b32b9c4
Compare
aeb9897
to
b23dfb7
Compare
/test |
deecdc6
to
8bdf10c
Compare
Related:cilium#32274 Co-authored-by: Ryan Drew <learnitall0@gmail.com> Signed-off-by: davchos <dchosrova@gmail.com>
8bdf10c
to
683210d
Compare
/test |
@glrf , @squeed, @learnitall @kaworu, |
Patch LGTM, thanks @glrf for following up and reviewing. Added the |
@davchos Could you address the conflicts when you get a chance? Thank you! |
I try to find some time this week. |
Signed-off-by: David Chosrova <dchosrova@gmail.com>
Well I think it is best to close this PR and work on a new one. If I find time I will try to resubmit a new one. |
Remove deprecated call to DialContext in Hubble server
Related:#32274, #33065
Signed-off-by: David Chosrova dchosrova@gmail.com