Hi @Aaina26. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Aaina26
Once this PR has been reviewed and has the lgtm label, please assign jpbetz for approval. For more information see the Code Review Process.

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

/sig api-machinery

/lgtm
/triage accepted

LGTM label has been added.

pull-kubernetes-unit failed due to my changes which I have corrected.
But before I commit those changes, I want to confirm following for pull-kubernetes-linter-hints failure:

• It suggests usage of %w instead of %v to wrap an error in fmt.Errorf. But this is not related to my change. It would require changing third %v placeholder to %w. If it is okay to do so, I can make the change and add it to my commit so that this test passes

New changes are detected. LGTM label has been removed.

/release-note-none

/kind bug

Hi @siyuanfoundation! I fixed the tests. Please take a look.

/ok-to-test

@jpbetz @deads2k for review.

I have changed the placeholder to "%w" where error was being wrapped. Although,I checked with my previous commit and the test had passed in my local but not when I committed. I am curious to know why that happened.

./hack/verify-golangci-lint.sh
installing golangci-lint and logcheck plugin from hack/tools into /home/necuser/k8_project/kubernetes/_output/local/bin
running /home/necuser/k8_project/kubernetes/_output/local/bin/golangci-lint run --color=always --config=/home/necuser/k8_project/kubernetes/hack/golangci.yaml ./... ./staging/src/k8s.io/api/... ./staging/src/k8s.io/apiextensions-apiserver/... ./staging/src/k8s.io/apimachinery/... ./staging/src/k8s.io/apiserver/... ./staging/src/k8s.io/cli-runtime/... ./staging/src/k8s.io/client-go/... ./staging/src/k8s.io/cloud-provider/... ./staging/src/k8s.io/cluster-bootstrap/... ./staging/src/k8s.io/code-generator/... ./staging/src/k8s.io/component-base/... ./staging/src/k8s.io/component-helpers/... ./staging/src/k8s.io/controller-manager/... ./staging/src/k8s.io/cri-api/... ./staging/src/k8s.io/cri-client/... ./staging/src/k8s.io/csi-translation-lib/... ./staging/src/k8s.io/dynamic-resource-allocation/... ./staging/src/k8s.io/endpointslice/... ./staging/src/k8s.io/externaljwt/... ./staging/src/k8s.io/kms/... ./staging/src/k8s.io/kube-aggregator/... ./staging/src/k8s.io/kube-controller-manager/... ./staging/src/k8s.io/kube-proxy/... ./staging/src/k8s.io/kube-scheduler/... ./staging/src/k8s.io/kubectl/... ./staging/src/k8s.io/kubelet/... ./staging/src/k8s.io/metrics/... ./staging/src/k8s.io/mount-utils/... ./staging/src/k8s.io/pod-security-admission/... ./staging/src/k8s.io/sample-apiserver/... ./staging/src/k8s.io/sample-cli-plugin/... ./staging/src/k8s.io/sample-controller/...
Congratulations! All files are passing lint :-)

Hi @jpbetz @siyuanfoundation @deads2k ,
Could you please take a look, so that this PR will be merged?

Thanks!

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale