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

k8s: Use slim Node in LocalNode Resource and K8s watchers #25282

Merged
merged 2 commits into from May 23, 2023

Conversation

joamaki
Copy link
Contributor

@joamaki joamaki commented May 5, 2023

We were performing unnecessary conversions from corev1.Node to slim_corev1.Node.
Only blocker for using slim_corev1.Node was the missing ProviderID.

@maintainer-s-little-helper maintainer-s-little-helper bot added the dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. label May 5, 2023
@joamaki joamaki added the release-note/misc This PR makes changes that have no direct user impact. label May 5, 2023
@maintainer-s-little-helper maintainer-s-little-helper bot removed the dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. label May 5, 2023
@joamaki joamaki self-assigned this May 5, 2023
@joamaki joamaki changed the title k8s: Use slim Node in resource and watchers k8s: Use slim Node in LocalNode Resource and K8s watchers May 5, 2023
@joamaki
Copy link
Contributor Author

joamaki commented May 5, 2023

/test

@joamaki joamaki marked this pull request as ready for review May 5, 2023 12:59
@joamaki joamaki requested review from a team as code owners May 5, 2023 12:59
Copy link
Member

@nebril nebril left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@joamaki
Copy link
Contributor Author

joamaki commented May 15, 2023

/test

@joamaki
Copy link
Contributor Author

joamaki commented May 16, 2023

/test

@joamaki joamaki added the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label May 16, 2023
@aditighag
Copy link
Member

@joamaki None of the e2e tests were triggered for your last test command. Is that expected? Would we need to close and reopen the PR so that all the tests are forcefully triggered?

The struct wrapping and boxing of resource creates an unnecessary
pointer indirection. Just newtyping Resource[T] is enough.

Signed-off-by: Jussi Maki <jussi@isovalent.com>
The LocalNode resource now uses slim_corev1.Node which avoids the
unnecessary conversions to it from v1.Node.

Adds ProviderID to slim_corev1.Node as it was needed by BGP.

Signed-off-by: Jussi Maki <jussi@isovalent.com>
@joamaki joamaki removed the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label May 17, 2023
@joamaki
Copy link
Contributor Author

joamaki commented May 17, 2023

@joamaki None of the e2e tests were triggered for your last test command. Is that expected? Would we need to close and reopen the PR so that all the tests are forcefully triggered?

Huh, that's odd. I'll rebase and try again and if that doesn't do it, I'll close and reopen.

@joamaki
Copy link
Contributor Author

joamaki commented May 17, 2023

/test

@maintainer-s-little-helper maintainer-s-little-helper bot added the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label May 22, 2023
@borkmann borkmann merged commit 48eeff4 into cilium:main May 23, 2023
58 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-to-merge This PR has passed all tests and received consensus from code owners to merge. release-note/misc This PR makes changes that have no direct user impact.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants