Wei
BTW, if define it in `ReplicaScheduling`, but without any `labelSelector`, users need to set each clusers' priority one by one. will it make configuration complex? or we should give this...
If the scheduling policy is considered, the following scenarios are involved: ||clusters' priority is configured|clusters' priority is not configured|user story| |--|--|--|--| |Duplicated|Behaving the same way now|Behaving the same way now||...
cc @Poor12
/assign @RainbowMango
cc @RainbowMango
Can I take this? @dprotaso
I think only change the logic in knative serving is better. Because if change `go-containerregistry`, the API return results will be changed, it has influence with who use `go-containerregistry`: ```go...
`go-containerregistry` maintainer tries to work on abother approach, when finished, I will sync and add ut for this issue
cc @psschwei @mattmoor @dprotaso
@mattmoor looks the same core mind with traceId, but it's quite difficult to implement with traceid(from my first mind), the advantage is less configuration and user-friendly. Which implementation way do...