In order to improve performance on commands like draft history, it would be nice if there was some way to store build information locally rather than through the kubernetes API as configmaps via pkg/storage/kube.
@fibonacci1729, I know you had ideas around storing build information in a git-based storage backend. When you have some free time, would you mind dumping your thoughts in this ticket?
In order to improve performance on commands like
draft history
, it would be nice if there was some way to store build information locally rather than through the kubernetes API as configmaps viapkg/storage/kube
.