-
Notifications
You must be signed in to change notification settings - Fork 130
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
Reduce number of annotations Chains stores in CRD objects #1076
Comments
@wlynch, Could you help with further details on this issue. As per initial analysis, apart from the following standard annotations: Below is the approach we could take:
In a case where the storage type is tekton( The intention of which i assume is to use an inbuilt cluster storage) - we could design a new CR to capture the key values as new CR specs. Please add your views and any additional items to be considered |
Feature request
It could be useful to add flags to reduce the # of annotations in CRD objects so we don't push etcd object limits.
cert trust roots should generally be loaded out of band for verification, so
chains.tekton.dev/cert
andchains.tekton.dev/chain
aren’t really needed (but are useful for debugging).chains.tekton.dev/payload
could be removed if we could deterministically reconstruct it later. We’d need information like what version of chains generated the provenance in it’s place.Use case
See https://tektoncd.slack.com/archives/C015FAQV290/p1710249674292949
The text was updated successfully, but these errors were encountered: