Shoubhik Bose

Discussion in the grooming: * Eventually, build's .status will probably go away since we'll be moving the validation to a webhook. * Therefore, it makes more sense to move the...

Brief discussion at grooming [sasha/shoubhik]: * Document using multiple credentials in the same secret, such that the secret is referenced in one of the existing API endpoints in the CRD....

How about we hardcode the builder in the BuildStrategy itself - because the builder is kinda everything. If the builder changes the BuildStrategy container steps might change too? In build...

We haven't modelled well enough how we should be "overriding" values from a Build to the ones in BuildStrategy. That's a nice design effort that should be undertaken with care...

However, yes, to begin with, let's make spec.builder optional and set the value of the of the builder image in the BuildStrategy itself for buildpacks.

https://skaffold.dev/docs/references/yaml/ Even though the API objectives are different, the API sheds light on key attributes for popular strategies.

By Build API , I mean the Build CRD. And as per the project's promise, it's Kubernetes-native :)

It's kinda similar in idea, but in case of Build it's more of a loosely typed way to define parameterized values. Imagine a build strategy which needs user input which...

If there are specific params which all build strategies share in a non-optional way, then that param should most likely be a strongly typed API attribute.