Creating pipeline at cluster level scope

[krishnaraman001]

Feature request

Is it possible to create a pipeline at cluster level scope?

Use case

We want to create a standard pipeline which can be used by all the teams who are spread across different namespaces, and also to avoid creating the same pipeline in all namespaces.

we are slowly moving our CI/CD to tekton, but it will more help full if the above use case can be achieved.

[lbernick]

Hi @krishnaraman001, thanks for filing this issue! This looks like a duplicate of #1876.

[krishnaraman001]

@lbernick I have gone through the #1876, is that feature got implemented or still discussions are going on?
it will be more easy for us if we are able to create a pipeline at cluster level, because most of the teams follow the same pipeline created.

[lbernick]

Cluster scoped pipelines haven't yet been implemented. We haven't decided yet on the future of ClusterTask, but the functionality you describe in your use case will eventually be provided by remote resolution (see TEP-0060, which was recently marked as implementable).

[tekton-robot]

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]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
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 rotten

Send feedback to tektoncd/plumbing.

[tekton-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

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.