-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove leader election patch #301
Labels
area/release
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
Comments
knative-prow-robot
added
the
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
label
Oct 15, 2020
@pierDipi: Closing this issue. 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. |
pierDipi
pushed a commit
to pierDipi/eventing-kafka-broker
that referenced
this issue
Jun 16, 2022
matzew
pushed a commit
to matzew/eventing-kafka-broker
that referenced
this issue
Jun 20, 2022
pierDipi
pushed a commit
to pierDipi/eventing-kafka-broker
that referenced
this issue
Jun 21, 2022
* Annotation for external topics Signed-off-by: Matthias Wessendorf <mwessend@redhat.com> * 💄 we want this as a real feature, removing the 'x-' flag Signed-off-by: Matthias Wessendorf <mwessend@redhat.com> * Fallback mechanism for the old external topic annotation for broker (knative-extensions#301) Co-authored-by: Ali Ok <aliok@redhat.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/release
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
See #293 (comment)
We should monitor upstream fixes: kubernetes/kubernetes#91942
/lifecycle frozen
The text was updated successfully, but these errors were encountered: