update BASEIMAGE to debian-base:bullseye-v1.4.2

[justdan96]

This is the latest Debian Bullseye image, it is the same as used in other Kubernetes projects, i.e. https://github.com/kubernetes-sigs/blob-csi-driver/pull/765/files

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: justdan96 / name: Dan (de33c80)

[k8s-ci-robot]

Welcome @justdan96!

It looks like this is your first PR to kubernetes/node-problem-detector 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/node-problem-detector has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @justdan96. 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.

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/test-infra repository.

[justdan96]

Any update on this @Random-Liu or @xueweiz ?

[justdan96]

/assign @dchen1107

[justdan96]

pinging @dchen1107 for approval

[justdan96]

/cc @vteratipally

Can we get an /lgtm on this?

[vteratipally]

/ok-to-test

Did you test the changes locally?

[justdan96]

I've got a fix for the failing build, tested on my machine using the commands below:

make docker-builder
make build-in-docker
make build-container

[justdan96]

@vteratipally it looks like that pull-npd-e2e-node test is failing for other PRs as well, can we proceed without it?

[vteratipally]

@vteratipally it looks like that pull-npd-e2e-node test is failing for other PRs as well, can we proceed without it?

Yes, it is a new failure, I will take a look.

[justdan96]

Is this okay to be merged until the test is fixed?

[justdan96]

@vteratipally is it okay to merge as-is?

[vteratipally]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: justdan96, vteratipally

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:

• OWNERS [vteratipally]

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

[vteratipally]

/test pull-npd-e2e-node

[vteratipally]

@vteratipally is it okay to merge as-is?

Sorry for the delay, yes it is