Skip to content

Fix gRPC listener error message and some minor (subjective) renaming #132545

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

Merged

Conversation

gauravkghildiyal
Copy link
Member

What type of PR is this?

/kind bug
/kind cleanup

What this PR does / why we need it:

  • Minor fix to log the correct path for which the listener failed to get created in staging/src/k8s.io/dynamic-resource-allocation/kubeletplugin/nonblockinggrpcserver.go
  • Rest is some subjective renaming at an attempt to distinguish the endpoints for the driver and the registration server. (I'd be willing to revert it if people feel otherwise.)

Does this PR introduce a user-facing change?

NONE

/wg device-management

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. kind/bug Categorizes issue or PR as related to a bug. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. wg/device-management Categorizes an issue or PR as relevant to WG Device Management. labels Jun 26, 2025
@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Jun 26, 2025
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Jun 26, 2025
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added the needs-priority Indicates a PR lacks a `priority/foo` label and requires one. label Jun 26, 2025
@k8s-ci-robot k8s-ci-robot requested review from bart0sh and klueska June 26, 2025 03:03
@k8s-ci-robot k8s-ci-robot added the sig/node Categorizes an issue or PR as relevant to SIG Node. label Jun 26, 2025
@@ -30,12 +30,12 @@ type nodeRegistrar struct {
}

// startRegistrar returns a running instance.
func startRegistrar(logger klog.Logger, grpcVerbosity int, interceptors []grpc.UnaryServerInterceptor, streamInterceptors []grpc.StreamServerInterceptor, driverName string, supportedServices []string, socketpath string, pluginRegistrationEndpoint endpoint) (*nodeRegistrar, error) {
func startRegistrar(logger klog.Logger, grpcVerbosity int, interceptors []grpc.UnaryServerInterceptor, streamInterceptors []grpc.StreamServerInterceptor, driverName, driverEndpointPath string, supportedServices []string, pluginRegistrationEndpoint endpoint) (*nodeRegistrar, error) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Moving the parameters looks like an unnecessary change. What's the rationale?

Renaming it is fine, but perhaps let's use "draEndpointPath"? That matches how it is called in the caller.

"driver endpoint" is still vague, a driver has multiple endpoints.

Copy link
Member Author

Choose a reason for hiding this comment

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

Haha! Sorry yes that was just a bit of an opinionated preference. I liked the idea that the "driver name" and the "driver path" are together and consecutive, like it is in the registrationServer and PluginInfo structs. But I can understand that is a very superfluous thing to do.

Reverted back the order and renamed as suggested to "draEndpointPath"

Copy link
Contributor

Choose a reason for hiding this comment

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

One can also argue that driverEndpointPath and pluginRegistrationEndpoint should be close together... but at this point not making more changes than really necessary trumps slight personal preferences.

Copy link
Member Author

Choose a reason for hiding this comment

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

Yep yep. Fair enough :)

@pohly pohly moved this from 🆕 New to 👀 In review in Dynamic Resource Allocation Jun 26, 2025
@gauravkghildiyal gauravkghildiyal force-pushed the kubeletplugin-grpcsetup branch from 4a82906 to a251fe0 Compare June 26, 2025 08:29
Copy link
Contributor

@pohly pohly left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve
/hold

For squashing into one commit.

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 27, 2025
@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jun 27, 2025
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: bffdcf469b4ac4310416865b1b2c0e26e7da5a6e

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gauravkghildiyal, pohly

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 27, 2025
- fix: Use correct path in kubeletplugin's gRPC listener error message
- chore: Rename socketpath for slightly improved distinction from pluginRegistrationEndpoint
@gauravkghildiyal gauravkghildiyal force-pushed the kubeletplugin-grpcsetup branch from a251fe0 to 3eefb05 Compare June 27, 2025 18:50
@gauravkghildiyal
Copy link
Member Author

Thank you for reviewing!

/unhold Squashed the commits as per suggestion.

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 27, 2025
@k8s-ci-robot k8s-ci-robot merged commit a23bace into kubernetes:master Jun 27, 2025
18 checks passed
@k8s-ci-robot k8s-ci-robot added this to the v1.34 milestone Jun 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/bug Categorizes issue or PR as related to a bug. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. release-note-none Denotes a PR that doesn't merit a release note. sig/node Categorizes an issue or PR as relevant to SIG Node. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. wg/device-management Categorizes an issue or PR as relevant to WG Device Management.
Projects
Status: 👀 In review
Development

Successfully merging this pull request may close these issues.

3 participants