-
Notifications
You must be signed in to change notification settings - Fork 83
Promote KafkaChannel to v1 #388
Comments
This issue is stale because it has been open for 90 days with no |
/remove-lifecycle stale |
This issue is stale because it has been open for 90 days with no |
/reopen |
@pierDipi: Reopened 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. |
/triage accepted |
…ions#388) * [0.25] KafkaChannel to init offsets before dispatcher (knative-extensions#913) * Cherry pick 3f2a9d7 [0.24] KafkaChannel to init offsets before dispatcher (knative-extensions#886) * ./hack/update-codegen.sh * [0.25] KafkaChannel dispatcher offset checking improvements (knative-extensions#929) * Fix Kafka channel event loss during subscription becoming ready * Make it look like knative-extensions#926
Problem
KafkaChannel should be promoted to v1. Would be best as a follow up on after the refactorings and unifications:
Persona:
Persona:
Which persona is this feature for?
Exit Criteria
A measurable (binary) test that would indicate that the problem has been resolved.
Time Estimate (optional):
How many developer-days do you think this may take to resolve?
Additional context (optional)
Add any other context about the feature request here.
The text was updated successfully, but these errors were encountered: