Activate blockade plugin for the k8s.io repo

[upodroid]

I forgot to activate the plugin in #29052

/cc @BenTheElder @dims

Will this work on existing PRs or just new PRs?

[BenTheElder]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BenTheElder, upodroid

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:

• config/OWNERS [BenTheElder]

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

[BenTheElder]

Will this work on existing PRs or just new PRs?

It should work on pushes, it will not crawl previous changes though.

[BenTheElder]

specifically these types of events incoming:

test-infra/prow/plugins/blockade/blockade.go

Lines 150 to 154 in e58df62

	if pre.Action != github.PullRequestActionSynchronize &&
	pre.Action != github.PullRequestActionOpened &&
	pre.Action != github.PullRequestActionReopened {
	return nil
	}

[BenTheElder]

/skip

[BenTheElder]

hmm /skip doesn't work while running perhaps?
/override pull-test-infra-integration
(optional presubmit, not that relevant here, slowest presubmit, we want to get this blockade in place ASAP)

[k8s-ci-robot]

@BenTheElder: Overrode contexts on behalf of BenTheElder: pull-test-infra-integration

In response to this:

hmm /skip doesn't work while running perhaps?
/override pull-test-infra-integration
(optional presubmit, not that relevant here, slowest presubmit, we want to get this blockade in place ASAP)

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.

[k8s-ci-robot]

@upodroid: Updated the plugins configmap in namespace default at cluster test-infra-trusted using the following files:

• key plugins.yaml using file config/prow/plugins.yaml

In response to this:

I forgot to activate the plugin in #29052

/cc @BenTheElder @dims

Will this work on existing PRs or just new PRs?

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.

[BenTheElder]

only 25 PRs open in k8s.io currently, we can take a quick pass

[BenTheElder]

commenting doesn't trigger it, close / reopen looks like it would

[BenTheElder]

forced the handful of existing open PRs with label:area/k8s.gcr.io to be blockaded by close + reopen with a note.

none remaining without the blockade:
https://github.com/kubernetes/k8s.io/pulls?q=is%3Apr+is%3Aopen+-label%3Ado-not-merge%2Fblocked-paths+label%3Aarea%2Fk8s.gcr.io

[BenTheElder]

affected PRs: https://github.com/kubernetes/k8s.io/pulls?q=is%3Apr+label%3Ado-not-merge%2Fblocked-paths+is%3Aopen

there are only 8

[BenTheElder]

there are other PRs that somehow don't have the label:area/k8s.gcr.io?

kubernetes/k8s.io#4948

[BenTheElder]

I think 4948 was the only PR that touched k8s.gcr.io/ but didn't have the area label.

remaining PRs look fine https://github.com/kubernetes/k8s.io/pulls?q=is%3Apr+is%3Aopen+-label%3Ado-not-merge%2Fblocked-paths+