[BUG] Multi-arch ClusterBuildStrategy has Namespace Scoped Resources

[adambkaplan]

Is there an existing issue for this?

• I have searched the existing issues

Kubernetes Version

v1.31.z

Shipwright Version

v0.14.0

Current Behavior

The multi-arch cluster build strategy includes namespace-scoped roles and rolebindings. This made it challenging to deploy with the Shipwright operator

Expected Behavior

Cluster build strategy examples should only include cluster-scoped resources in manifests.

Steps To Reproduce

Deploy the cluster samples for v0.14.0 release using kubectl apply -f:

kubectl apply --filename https://github.com/shipwright-io/build/releases/download/v0.14.0/sample-strategies.yaml --server-side

Sample strategies will include namespace-scoped roles and rolebindings.

Anything else?

No response

[adambkaplan]

Adding this to the v0.15.0 backlog - keeping this build strategy cluster-scoped broke the operator when we tried to import the latest set of sample build strategies.

Moving this to be a namespace-scoped build strategy should fix the issue on the operator side.