Adam Kaplan

@khrm something that we need to consider is backwards compatibility. Results can be backwards-compatible if we provide an option for v1beta1 reconciliation. That won't be the case if we only...

/lifecycle frozen :thinking: I wonder if we need a TEP to discuss this. We currently reconcile v1beta1 APIs across the board. We could employ similar techniques that k8s does if...

This creates an interesting challenge for long-running instances. When we switch to reconcile with v1 objects, the database will have some information as v1, and others as v1beta1. This can...

> This sounds a bit like the storage version migrator but for the results db: https://github.com/kubernetes-sigs/kube-storage-version-migrator/blob/master/USER_GUIDE.md Exactly!

Something to consider is that we will want to support delegated log forwarding (say, via fluentd). This was called out as a potential long-term feature in [TEP-0117](https://github.com/tektoncd/community/blob/main/teps/0117-tekton-results-logs.md#implementation-plan). I've filed #619...

/lifecycle frozen

/remove-lifecycle stale This is still a valid concern.

/lifecycle frozen I agree that having a "v1" that applies to the whole installation makes a lot of sense. I will ~~mark namespace-level features as out of scope so it...

The e2e suite also needs to verify that we are enforcing SAR checks correctly. Especially in light of #249, we need to make sure that users can't access results that...

/remove-lifecycle stale /lifecycle frozen