Skip to content
This repository has been archived by the owner on Jun 19, 2022. It is now read-only.

Use assignment label to select which BrokerCell should service a Broker #1808

Closed
grantr opened this issue Oct 6, 2020 · 2 comments
Closed
Labels
area/broker kind/feature-request New feature or request lifecycle/stale priority/2 Nice to have feature but doesn't block current release defined by release/* release/2
Milestone

Comments

@grantr
Copy link
Contributor

grantr commented Oct 6, 2020

Problem
In #866 we'll define a label or annotation that assigns a Broker to a BrokerCell. The BrokerCell controller should use this value to decide which BrokerCell should service a broker, and in which targets configmap the broker's targets should be contained.

Exit Criteria
Brokers are serviced by the BrokerCell identified in their metadata

Additional context (optional)
Not strictly blocked by #866, but blocked by the decision about which key will be used to denote this assignment.

@grantr grantr added kind/feature-request New feature or request area/broker labels Oct 6, 2020
@grantr
Copy link
Contributor Author

grantr commented Oct 6, 2020

Also part of this: adding assignment awareness to the Broker controller so it can decide which BrokerCell determines readiness and Broker address.

@grantr grantr added priority/2 Nice to have feature but doesn't block current release defined by release/* release/2 labels Oct 13, 2020
@grantr grantr added this to the Backlog milestone Oct 13, 2020
@github-actions
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/broker kind/feature-request New feature or request lifecycle/stale priority/2 Nice to have feature but doesn't block current release defined by release/* release/2
Projects
None yet
Development

No branches or pull requests

1 participant