PipelineRuns are all in kabanero namespace

[ianpartridge]

Currently, when the pipelines execute, it always occurs in the kabanero namespace (the PipelineRun CR exists in that namespace). This means that pipeline executions from all different workloads are jumbled together making it very difficult to distinguish between them.

A better approach would be for pipelines to run in the namespace that they are deploying into.

For example, if the user has added:

spec:
  targetNamespaces:
  - my-app

to their Kabanero CR, the pipeline could run in the my-app namespace. This would give the user ownership over their PipelineRun and make usage and investigation much clearer.

[ianpartridge]

This does mean that the build would consume resources in the deployment namespace which is perhaps not ideal. We could look at other approaches, let's keep the issue for the root problem of the indistinguishability of PipelineRuns in the kabanero namespace.

[kaczyns]

We have been trying to introduce the concept of a pipeline namespace (a single one) that runs builds. It is not desirable to have the builds running in the control namespace (kabanero), nor do I think it's desirable to have them running in the app deploy namespaces, although I can see how that would be convenient on some levels.

Please have a look at kabanero-io/kabanero-operator#230 and let us know if this addresses some of your concerns.

[ianpartridge]

Thanks @kaczyns - closing in favour of kabanero-io/kabanero-operator#230