Yuwen Ma

cc @briandealwis

One big advantage for option 3: Once users accept the idea of using canonical format to represent their non KRM app config, they can build logic between the non KRM...

ConfigSync uses an annotation (ConfigMap hash) to detect ConfigMap change and re-apply the referrer resources

I think it's a fair point that `set-image` should accept Container `.name` as the matcher besides Container `.image`. "4. ...or what if container name is not specified" --> Container `.name`...

+100. This can also help users understand what we are talking about and be more involved.

Very looking forward to this. I'd like to refer to this issue when answering the user questions regarding how to use setters for XXX.

Tasks: - [feat]scaffolding: #2392 - [docs] Re-write kpt.dev starlark guide - [feat] Define test framework if users contribute to kpt catalog. - [feat] make `resource_list.items` as strong typed objects (protobuf)....

User experience compared to Helm: - helm users are more easy to get started. They only edit `values.yaml` file (with enough comment, they can even only rely on the values.yaml...

Some updates: we did POC about same-merge behavior of non-KRM files Demo1: [drive.google.com/file/d/1BMYH3HcTzUcnSTk0iO0oO_O4O_RiUhF7/view](https://drive.google.com/file/d/1BMYH3HcTzUcnSTk0iO0oO_O4O_RiUhF7/view) The graph below explains the high level workflow, more context can be found in the [CUJ](https://docs.google.com/document/u/1/d/1ut_kCxAd01mg3s9fkSyUipWpauTxOMARL2zBUYIBgTo/edit?urp=gmail_link#heading=h.xx2hi3k95ry8) and...

> Another issue uncovered by #3292: kustomize identifier transformers keep track of previous identifiers in annotations, but not in an idempotent manner, and it also doesn't output the annotations. >...