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

Cloud events per namespace #7888

Open
meanderix opened this issue Apr 17, 2024 · 1 comment
Open

Cloud events per namespace #7888

meanderix opened this issue Apr 17, 2024 · 1 comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@meanderix
Copy link

meanderix commented Apr 17, 2024

Feature request

In our setup, we have a large number of namespaces, each with their own custom pipelines as well as their own event listeners.

As I understand, we are allowed to provide a single sink for cloud events by specifying default-cloud-events-sink in the config-defaults config map in the tekton-pipelines or openshift-pipelines namespaces (n.b. I suppose this has been changed to the config-events config map).

IMO this approach comes with some limitations:

  1. We are not able to customize the sink per namespace.
  2. We are not able to filter out events per namespace.
  3. This functionality also presumes that we have access to the tekton-pipelines or openshift-pipelines namespaces (in our environment this access is limited to the cluster admins).

Use case

It would be very useful to be able to respond to events such as pipeline completion by listening to these events (i.e. isolated per namespace). This could potentially initialize a separate pipelinerun (which is part of the design we are trying to implement).

@meanderix meanderix added the kind/feature Categorizes issue or PR as related to a new feature. label Apr 17, 2024
@meanderix
Copy link
Author

Related: #5208

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.
Projects
None yet
Development

No branches or pull requests

1 participant