Capture security concerns about pipeline-controller

[yiannistri]

Currently the pipeline-controller allows for cross-namespace references for applications and environments. We should capture any security concerns in this area.

[enekofb]

pairing with @sympatheticmoose

[enekofb]

working in the branch

weaveworks/weave-gitops-private#77 and

https://miro.com/app/board/uXjVPdlWbO0=/?share_link_id=150662081250

[lasomethingsomething]

@enekofb Do we know if this is still true? @squaremo

[squaremo]

Yep still true, and still a concern. https://github.com/weaveworks/pipeline-controller/blob/main/api/v1alpha1/pipeline_types.go#L218

[lasomethingsomething]

Two concerns:

• you need secrets (large blast radius)
• cross-name references sprinkled willy-nilly, problem in K8s

We should do something about this if we want Pipeline Controller to be GA.

Also part of Pipelines initiative.

[lasomethingsomething]

Closing--docs here. We should do something about this if we want Pipeline Controller to be GA. Also part of Pipelines initiative.”: Talk to Michael about feasibility.). Follow-up work to be captured in new issues:

• TODO: Remove the current cross-namespace reference we have
• “you need secrets (large blast radius). We should do something about this if we want Pipeline Controller to be GA. Also part of Pipelines initiative.”: Talk to @squaremo about feasibility.