Closed goern closed 2 years ago
Thanks for the issues.
The Tekton chains is the component of the tektoncd, and has it own CRDS.
The installation requires more privileges than just edit
in the openshift namespace.
we can document this step in the setup-instance
documentation on how to install tekton chains for the users.
However for our aicoe-ci instance which is running operate-first, needs to be installed with proper tekton chain CRDs submission to the operate-first.
I will check on the tekton chain and derive what we can install via our kustomize and what need to be directly installed with the CRDs.
There are further steps to be taken in regards to the chains setup. https://github.com/tektoncd/chains#setup
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
/remove-lifecycle stale
Tekton Chains is deployed on Operate First (https://github.com/operate-first/support/issues/438). The missing piece is the ability to push signatures to quay.io (see https://github.com/AICoE/summit-2021-octo-keynote/issues/28)
Tekton Chains is now all set up and working, and pushing image signatures to quay.io.
/close
@codificat: Closing this issue.
chains is pretty easy to add:
kubectl apply -f https://storage.googleapis.com/tekton-releases/chains/previous/v0.5.0/release.yaml
Originally posted by @lukehinds in https://github.com/AICoE/summit-2021-octo-keynote/issues/7#issuecomment-948775599
/kind feature /priority important-soon /assign harshad16 /assign screeley44 /kind demo