[release-0.1] cherrypick #4: add --leader-election-namespace flag

[xrstf]

Summary

#7 accidentally targeted the main branch, when it should have targeted release-0.1.

What Type of PR Is This?

/kind cleanup

Release Notes

Add `--leader-election-namespace` flag

[ntnn]

/lgtm
/approve

[kcp-ci-bot]

LGTM label has been added.

Details

Git tree hash: 36f7dfa47b41377db00b7b584d8c8ecb63a6e5c8

[xrstf]

/override pull-init-agent-test-e2e-kcp-0.27
/override pull-init-agent-test-e2e-kcp-0.28
/override pull-init-agent-test-e2e-kcp-0.29

These tests were defined as ProwJobs in the initial commit, but only later in #2 actually implemented. The 0.1 release branch does not have such tests. I never expecte to open a release branch this early, and now it's biting me a bit in the rear end 😬

[kcp-ci-bot]

@xrstf: Overrode contexts on behalf of xrstf: pull-init-agent-test-e2e-kcp-0.27, pull-init-agent-test-e2e-kcp-0.28, pull-init-agent-test-e2e-kcp-0.29

Details

In response to this:

/override pull-init-agent-test-e2e-kcp-0.27
/override pull-init-agent-test-e2e-kcp-0.28
/override pull-init-agent-test-e2e-kcp-0.29

These tests were defined as ProwJobs in the initial commit, but only later in #2 actually implemented. The 0.1 release branch does not have such tests.

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.

[xrstf]

/approve

[kcp-ci-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ntnn, xrstf

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [xrstf]

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