blockades: prevent direct changes to staging repos in kubernetes/k8s.io

[sAchin-680]

What type of PR is this?

/kind cleanup
/area prow

What this PR does / why we need it:

This PR introduces a new blockades rule to prevent direct modifications to the staging/ directories in the kubernetes/k8s.io repository.

These staging repos are intended to be mirrored from upstream sources (e.g., kubernetes/kubernetes), and changes should be made at the source instead. Blocking direct edits here helps maintain consistency, prevents configuration drift, and ensures changes follow the intended workflows.

Special notes for your reviewer:

• Consistent with existing blockades patterns defined in config.yaml
• The message clearly communicates where changes should be proposed instead

Does this PR introduce a user-facing change?

NONE

[k8s-ci-robot]

Welcome @sAchin-680!

It looks like this is your first PR to kubernetes/test-infra 🎉. 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/test-infra 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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sAchin-680
Once this PR has been reviewed and has the lgtm label, please assign priyankasaggu11929 for approval. For more information see the 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:

• config/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]

Hi @sAchin-680. 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-sigs/prow repository.

[sAchin-680]

Done as per your suggestion, replaced Go module import paths with actual GitHub repo names, and ensured client-go and other existing staging repos have matching config. Let me know if anything else needs adjustment!

[BenTheElder]

/ok-to-test
let's get the readme changes in, then this

[sAchin-680]

Hey @BenTheElder

While running the pull-test-infra-prow-checkconfig job, I encountered the following error:

• unknown field "missing_label_policy" in config/prow/plugins.yaml
• Strict is set and there were warnings.

Prow job link: https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/test-infra/34695/pull-test-infra-prow-checkconfig/1917219320614621184

It appears that missing_label_policy is not a recognized field in the current configuration schema, which is causing the check to fail due to --strict.

Should I go ahead and remove this field from the config, or is there an updated way to define this policy?

[BenTheElder]

we should probably fold this into the same config as above?

also fyi @chrishenzie re: kubernetes/kubernetes#130799

[sAchin-680]

/test pull-test-infra-prow-checkconfig

[k8s-ci-robot]

@sAchin-680: The following test 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-test-infra-prow-checkconfig	52d564a	link	true	/test pull-test-infra-prow-checkconfig

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

[BenTheElder]

if possible we should avoid all the formatting changes on existing entries

[BenTheElder]

this config looks wrong, as do the lines below

I generated this: kubernetes/kubernetes#131351