CCO-388: operator/cmd: allow configuring the leader election namespace #636
Conversation
In HyperShift and similar deployment topologies, the leader election lock for this operator will not be in the core namespace for the host, but in the tenant namespace. Signed-off-by: Steve Kuznetsov <skuznets@redhat.com>
openshift-ci-robot
added
the
jira/valid-reference
|
@stevekuznetsov: This pull request references CCO-388 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.15.0" version, but no target version was set. In response to this:
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. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: stevekuznetsov The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/hold |
openshift-ci
bot
added
the
do-not-merge/hold
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #636 +/- ##
=======================================
Coverage 48.42% 48.42%
=======================================
Files 96 96
Lines 11741 11741
=======================================
Hits 5686 5686
Misses 5425 5425
Partials 630 630 |
|
@stevekuznetsov: The following test failed, say
Full PR test history. Your PR dashboard. 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. |
In HyperShift and similar deployment topologies, the leader election lock for this operator will not be in the core namespace for the host, but in the tenant namespace.