nrt-api: Update publishing-bot rules.yaml

[swatisehgal]

rules.yaml captures the dependencies of code in the staging repo and is used by
the publishing-bot to publish the staging repository.

Signed-off-by: Swati Sehgal [email protected]

What type of PR is this?

Updates publishing-bot rules to ensure noderesourcetopology-api staging repo is published.

/kind cleanup

What this PR does / why we need it:

Depends on #110252. This change is to ensure that testing in CI (specifically the pull-publishing-bot-validate test) runs with the right rules.yaml configuration.

Which issue(s) this PR fixes:

Special notes for your reviewer:

Please refer to this comment for context.

Does this PR introduce a user-facing change?

NONE

[k8s-ci-robot]

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

[swatisehgal]

/cc @dims

[swatisehgal]

/sig node

[dims]

@swatisehgal the other one has to merge first then this one.

[swatisehgal]

@swatisehgal the other one has to merge first then this one.

Thanks @dims for clarifying this. I might have misunderstood earlier but all good now. Both the PRs (and their description) have been updated.

[kad]

is that chunk intentional?

[swatisehgal]

Ah, I think this was a mistake. Let me fix it. Thanks for that @kad.

[dims]

Are we picking this up in 1.26 @swatisehgal ?

[swatisehgal]

Are we picking this up in 1.26 @swatisehgal ?

Yep, that's the plan. Will polish this in the coming days.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: swatisehgal
Once this PR has been reviewed and has the lgtm label, please assign nikhita for approval by writing /assign @nikhita in a comment. For more information see:The Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• staging/publishing/OWNERS

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]

@swatisehgal: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-publishing-bot-validate	17db4c1	link	false	/test pull-publishing-bot-validate
pull-kubernetes-verify	17db4c1	link	true	/test pull-kubernetes-verify

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

[swatisehgal]

The failures in CI are because this PR depends on #110252. These should get resolved once the aforementioned PR is merged.

[k8s-ci-robot]

@swatisehgal: PR needs rebase.

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.

[swatisehgal]

/close

as this was merged in #110252.

[k8s-ci-robot]

@swatisehgal: Closed this PR.

In response to this:

/close

as this was merged in #110252.

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.