Brian Grant
Brian Grant
cc @natasha41575 @droot @yuwenma
For cases where there is a specific KRM type that maps to a specific function, as with ApplyReplacements, my preferred solution is a function catalog mechanism, so that it doesn't...
Filed #3339 for the catalog-based mapping mechanism. Are there other use cases where a selector would be desirable? In general, I do think we need more flexibility with respect to...
A good point was raised in slack: https://kubernetes.slack.com/archives/C0155NSPJSZ/p1656746811019709 It seems more appropriate to use KRM-based references and selectors than file paths. We need to think about how this would interplay...
This is about generation of packages rather than deployment of packages.
Porch is server side. The "package set" proposal I was referring to was Morgante's.
With respect to functions "winning": I want functions to win, in the case that they are intended to act as mutating admission control. This is the "inner" model of extension:...
Regarding coupling functions to packages: I explicitly do not want to require writing new functions for every package. At that point, one might as well use one of the "as...
"A blueprint package has a set of recommended & required functions" Not all functions used on resources in a package need to be specified in the Kptfile. Imperative generation and...
"kpt packages produce the same result as running kubernetes with corresponding admission controllers and controllers" -- this is a good starting point for how to think about it. This diagram...