Tom Kennedy

> > @SaschaSchwarze0 do you have any plans to continue working on this PR? Looking forward to this change! > > > > Sure, but beside asking for it, maybe...

Good catch!

Same problem here: core version 2022.6.6

The only thing that's not open source is the creation of the builder image. I would need to investigate what we have to do to support that. As of right...

But the builder image itself is completely public and the windows builds are public in the GitHub actions ci for kpack.

kpack does not support creating a builder without a clusterstack. As of 0.11.0 you can create without a clusterstore but the buildpack resources will need to be available to satisfy...

There is an interesting idea in this that we haven't really talked much about historically which is the idea of a multicluster kpack where you have some control cluster that...

It looks like the long time to reconcile builders might be due to the buildpacks in the clusterstore being in a different registry than where the builder is being written...

@chenbh can we merge this?

My main concern with this would be perpetual retries even for issues that should be terminal like compilation failures. We have been tossing around the idea of retrying particular steps...