Sunil Arora

/cc @ChristopherFry @bgrant0607

> The original issue was https://github.com/GoogleContainerTools/kpt/issues/2577, which lists some examples of tools that support similar operations. Ack. Will take a quick look. > Either way, once that information is known,...

> There's also: https://kubernetes.io/docs/reference/labels-annotations-taints/#kubectl-kubernetes-io-default-container Oh..this is interesting. Didn't know such a thing existed. So the default container annotation (if exists) can also be used to select the container in case...

Thanks for writing this. `Setters have kind of been an attractive nuisance` -- it captures the sentiment so well.

Thanks for starting this thread @johnbelamaric > A package needs a value from the runtime instantiation of another package (e.g., a load balancer IP address). Just a note: This one...

Slightly different but a common scenario: I have an application package that needs CloudSQL resource. And, CloudSQL resource is satisfied by another infra package that uses KCC resources (Config Connector)....

Great discussion in this thread. I created a CUJ to make some of these more concrete in context of `namespace provisioning` use-case https://github.com/GoogleContainerTools/kpt/issues/3294.

some quick thoughts wrt `kpt-merge`, whenever we create a new variant of a package, we need to track the identifier of upstream resources in the downstream package. This is sort...

> Good point, @droot. As discussed in #2544, when a package is cloned, it becomes the upstream to the new downstream, even if it was a downstream to its own...

/cc @karlkfi @mortent