Skip to content
This repository has been archived by the owner on Aug 2, 2023. It is now read-only.

Could not find the required trigger template or trigger bindings in namespace: tekton-pipelines. #291

Open
karimbzu opened this issue Feb 14, 2020 · 2 comments

Comments

@karimbzu
Copy link

karimbzu commented Feb 14, 2020

I have installed kabanero 0.5 successfully on OCP 4.2.14, but i am unable to create webhook because triggerbindings did not install in the "tekton-pipeline" namespace.
[root@bastion 0.5]# oc project
Using project "tekton-pipelines" on server "https://api.ocp.XX.6443/
[root@bastion 0.5]# oc get triggerbindings.tekton.dev
NAME AGE
monitor-task-binding 17m
I am using this guideline, https://kabanero.io/docs/ref/general/installation/installing-kabanero-foundation.html
Another thing, in my cluster the resource quota and limit ranges, are configured for each new project, therefore, instead of #oc new-project tekton-pipeline in the "install.sh" script the command should be either #oc adm new-project tekton-pipelines or #oc create namespace tekton-pipelines so that quota should not affect on the newly created resources in tekton-pipelines. Maybe the above mention triggerbindings issue is related to resource quota? Kindly advise me in this regard. Thanks

@karimbzu
Copy link
Author

Resolved the issue:
Uninstall everything,
Reinstall from scratch

@kaczyns
Copy link
Member

kaczyns commented Feb 19, 2020

Hi @karimbzu - in order to diagnose the original problem we would need to see the collection controller pod logs, to determine why the trigger bindings and trigger templates did not get installed into the tekton-pipelines namespace. Do you still have these logs available? Or is there a way that you can re-create the issue?

The install script is intended to be a sample that can be changed as required. It would be impossible for us to create an install script that could compensate for all of the ways a user can configure an OpenShift cluster. We certainly wouldn't want to do something that would over-ride the quota that an administrator had set up, because the administrator might now want the person installing Kabanero to over-ride the quota.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants