Jon Donovan

It should be possible for the Operator to calculate the safe upgrade path and follow it, yes. That seems like a good path forward to me. The Operator today doesn't...

> Our reconcilers implicitly do a lot of the upgrade logic today in that they gracefully handle new fields and default them actively for example. That work would need to...

/assign Cynocracy I didn't see this before hitting the corner case myself :) I have a hacky attempt at a fix in knative.dev/networking, if it works I can upstream it...

Does this still repro with the new k8s library versions? I was really hoping it did not :( Fake GOPATH sounds good, we've done similar things internally when we anger...

/remove-lifecycle stale

This reminded me of reading https://www.cockroachlabs.com/blog/go-file-size/ I don't know how up to date it is, but maybe it would be reasonable to consider another language if we wanted to minimize...

Gotcha 😃 That all makes sense to me! > While I think minimizing the binary is a nice goal, I also think there are practical considerations. I'm reminded of Kubernetes...

/assign Cynocracy

Some comments from slack: * Why Job definitions and not vendor in the go code? * Could we have a single image that knows how to do the upgrades in...

What about a single k8s Job per component that takes arguments of “to” (and maybe “from”) release, and within the Job code there’s a framework (like sharedinformer) which registers a...