Skip to content
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

[Cloudevents] Add a roadmap for the cloudevents controller #827

Open
afrittoli opened this issue Jan 26, 2022 · 6 comments
Open

[Cloudevents] Add a roadmap for the cloudevents controller #827

afrittoli opened this issue Jan 26, 2022 · 6 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@afrittoli
Copy link
Member

Feature request

Add a roadmap for the cloud events controller

Use case

We shall use this issue to collect ideas about where to go next with the controller, how to make it an official component of Tekton, which features we'd like to have, which use cases we'd like to address. We can condensate all of that into a roadmap.md.

@afrittoli afrittoli added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 26, 2022
@afrittoli
Copy link
Member Author

/cc @waveywaves

@drewbailey
Copy link

Something that is top of mind for us currently is the ability to have more granular control over the cloudevent sink that gets configured. The ability to support mTLS when sending events to a configured sink as emitting metrics around cloud events would be great.

@waveywaves
Copy link
Member

@drewbailey @afrittoli Created a integration roadmap in this issue LMKWYT

@tekton-robot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

@tekton-robot tekton-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 9, 2022
@afrittoli
Copy link
Member Author

/remove-lifecycle stale

@tekton-robot tekton-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 9, 2022
@afrittoli
Copy link
Member Author

/lifecycle frozen

@tekton-robot tekton-robot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label May 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
Status: Todo
Development

No branches or pull requests

4 participants