eventing
eventing copied to clipboard
[Feature Request] Ability to "Pause" Event Producing and Consuming resources.
Problem Sometimes you just need the system to stop churning. If we added a new duck type or something that had a setting to turn off the resource from producing or consuming events, we would enable use-cases like disaster recovery environments or even help contributors debug components without deleting resources.
Things that you might want to pause:
- Broker
- Trigger
- Flow resources
- Sources
- Sinks
- Channels
- Subscriptions
(basically all of the eventing ecosystem)
Persona: Which persona is this feature for? Operator mostly, but likely useful for Contributor.
Exit Criteria There is a setting in the spec of resources or configmap that cluster operators can use to pause/disable/stop event producers and consumers.
Time Estimate (optional): 2-4 weeks. This has a lot of edge cases.
Additional context (optional) This will be planned in [Public] Knative Eventing Pause Feature
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
.
/remove-lifecycle-stale
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
.
:(
We're going to need this so its possible we will pick it up. So have requested access to the doc.
There is an incoming updated doc for review.
👋 https://docs.google.com/document/d/1U9hzLngLswwbs4EHaTtbinAush2-1hVT4xA0EoIEfWE/edit is pretty much agreed on with some of the eventing team so I will be beginning work on the annotation-to-pause those components that produce events shortly.
Continue to provide feedback in the meantime, thanks!
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
.
Is there any update on this topic? I could not find a ticket or something that tracks the state