Version field for kapp app annotations

[ringerc]

Describe the problem/challenge you have

kapp's app deployments track the app's name, but do not record any version for the deployment to show in kapp list etc.

While it is possible to use ytt, kustomize's commonAnnotations etc to inject a kubernetes.io/version annotation into deployed resources, kapp doesn't know to look for it, and no version can be shown in kapp list. It would be immensely useful if kapp list provided an at-a-glance view of deployed component versions.

See fluxcd's flux get kustomization, Helm's helm list for other tools that present at-a-glance component version information.

Describe the solution you'd like

It would be very helpful if kapp deploy took an optional application version flag, which could also be injected as a kapp config stanza. This version would appear in kapp list.

kapp config could also be added that propagates the supplied version to kubernetes.io/version annotations on all components kapp is deploying. This should probably be off by default for compatibility reasons.

Anything else you would like to add:

---

Vote on this request

This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.

👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"

We are also happy to receive and review Pull Requests if you want to help working on this issue.

[renuy]

Hello @ringerc ,
Could you elaborate on the use case? This could fall in the scope of other tools under carvel, based on what you may be trying to achieve.

[ringerc]

@renuy The goal is at-a-glance visibility of deployed component versions that doesn't require locating some specific resource which may vary from deployed component to deployed component in order to inspect its annotations/labels.

I don't see a clean way to do this w/o support for it in kapp itself.