Andrew Bayer
Andrew Bayer
I'm pretty sure there's something weird about our CRDs and/or our packages resulting in this... EDIT: Ok, my best guess so far is that it's getting confused by the existence...
Yeah, I'm trying to figure out exactly where that assumption is made...
Ok, the panic is the same as in https://github.com/kubernetes-sigs/controller-tools/issues/624, though the scenario in that PR doesn't quite match ours...BUT! I have a tentative fix: https://github.com/abayer/controller-tools/commit/c8009f3483b75a66454a5b0ad89159ed40413c80 - I'm now working on...
PR opened for that fix - https://github.com/kubernetes-sigs/controller-tools/pull/627 - I'm now trying to determine if we need to filter some fields out, like the knative-specific branch does. I think at a...
/assign @abayer
Well, https://github.com/kubernetes-sigs/controller-tools/pull/627#issuecomment-931355857 - our layout is awfully nonstandard, and the not-unreasonable response from the maintainer is asking if we can restructure things rather than make a change to `schemapatch`. I...
Started playing around with what would be involved in moving `pkg/apis/resource/v1alpha1` and `pkg/apis/run/v1alpha1` and...well, so far, I don't think it's viable without mucking up our types pretty thoroughly.
So there's the additional problem that we can't guarantee structured resolution source information - that's going to depend on the resolver implementation itself. We can control that for `git`, `bundles`,...
This feels like it's on the right track!