-
Notifications
You must be signed in to change notification settings - Fork 117
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
Triggers ignore namespace attribute #1405
Comments
This also fails if you assume a single namespace and change your global prowjob_namespace, pod_namespace attributes to something besides
|
If I switch the tekton/controller.go namespace to be job.Spec.Namespace in various places, I again get failures do to kube owner references being cross namespaces... There are "namespace" fields all over the place, but it seems they all need to be the same? |
Did you ever solve this problem @treyhyde |
/kind question |
No, we gave up on lighthouse |
I know this is an old issue, but I think I found why this is (still) happening, but I'm not sure how to fix/test a change. maybe @ankitm123 or @abayer knows since they touched the tekton controller last... 😬 sorry for the ping. My question is, can we pull the namespace from triggerConfig like @treyhyde and I expected, rather than using the namespace that the lighthouseJob uses? I have a bit of go experience, but I don't know how to test these changes or add some breakpoints to inspect variables to pass the correct one in an actual deployment with other lighthouse components. This seems like a bug that forces one to install lighthouse in the same namespace that the tekton pipelineRun resources are running, and limits to that one namespace. |
For a trigger defined as
a LighthouseJob is created
however, the PipelineRun is created in the
lighthouse
namespace, notcypress-e2e
as I would expect.The text was updated successfully, but these errors were encountered: