self nominate ffromani to be a sig-node reviewer

[ffromani]

What type of PR is this?

/kind feature

What this PR does / why we need it:

self nominate @ffromani to be a sig-node reviewer

Which issue(s) this PR fixes:

Fixes #N/A

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

Per https://github.com/kubernetes/community/blob/master/sig-node/sig-node-contributor-ladder.md#reviewer

• contributing to the SIG from early 2020 to date
• kubernetes member since early 2021
• regular member of sig-node-ci subgroup
• contributing to the kubelet mostly focusing on the resource managers (cpu, device, topology) and e2e tests. By proposing myself as reviewe, I wish to step up and keep contributing in these areas but broaden the perspective to other areas of the kubelet
• PRs reviewed: https://github.com/kubernetes/kubernetes/pulls?q=is%3Apr+reviewed-by%3Affromani+label%3Asig%2Fnode+
• PRs authored: https://github.com/kubernetes/kubernetes/pulls?q=is%3Apr+author%3Affromani+label%3Asig%2Fnode+
• KEPs reviewed: https://github.com/kubernetes/enhancements/pulls?q=is%3Apr+reviewed-by%3Affromani+label%3Asig%2Fnode+
• KEPs authored: https://github.com/kubernetes/enhancements/pulls?q=is%3Apr+author%3Affromani+label%3Asig%2Fnode+

[ffromani]

/sig node

[swatisehgal]

Huge +1 (non-binding)

[ffromani]

/test pull-kubernetes-e2e-kind

[kannon92]

+1!

[pacoxu]

+1!

[pacoxu]

/cc @kubernetes/sig-node-leads

[k8s-ci-robot]

@pacoxu: GitHub didn't allow me to request PR reviews from the following users: kubernetes/sig-node-leads.

Note that only kubernetes members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

/cc @kubernetes/sig-node-leads

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.

[SergeyKanzhelev]

/lgtm

I totally support this self-nomination.

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 428a25875d9ca8931fdbf5ed0f623bc7f36ef50f

[dchen1107]

/lgtm
/approve

Thanks @ffromani for your contribution.

[ffromani]

/assign @thockin

per bot suggestion

[thockin]

Thanks and congrats!

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dchen1107, ffromani, SergeyKanzhelev, thockin

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 [thockin]

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

[aojea]

+1

[bart0sh]

/triage accepted
+1

[ffromani]

Thanks everyone for the +1s! Appreciate it a lot!

does this PR need to be added to a milestone? I don't mind waiting for the 1.31 cycle to start, but wondering if when the 1.31 cycle start we'd need the milestone-1.31 to be added here.

[pacoxu]

Release of v1.30 is schedule on April 17th.
/milestone v1.31

[bart0sh]

/assign @mrunalp @derekwaynecarr @dchen1107
for an approval