Provide a first-class API (as part of App CR status) for discovering deployed resources by App CR #430
Labels
carvel-accepted
This issue should be considered for future work and that the triage process has been completed
enhancement
This issue is a feature request
priority/awaiting-more-evidence
Lowest priority. Possibly useful, but not yet enough support to actually get it done.
What steps did you take:
PackageInstall
via kubectl (not usingkapp deploy
, I mean)App
via kubectl,kubectl get app my-app -oyaml
What happened:
The
App
does not have any labels/annotations.What did you expect:
I would have expected this App CR to have something like:
Anything else you would like to add:
This problem has been discussed at this Carvel community channel thread and there is a temporary workaround: get the ConfigMap whose name is
<appname>-ctrl
and get from the Data["spec"] the keylabelValue
.The motivation main motivation for having this annotation exposed by the App CR is for other clients (like, in my case, the Kubeapps project) to have bidirectional traceability of the resources created as a consequence of an App CR (regardless they're using Kapp or just plain kubectl calls).
Particulary, Kubeapps needs this to display to the users which Kubernetes resources are part of an installation.
Some examples and demo video on the Carvel bundles support in Kubeapps: vmware-tanzu/kubeapps#3816
Environment:
kubectl get deployment -n kapp-controller kapp-controller -o yaml
and the annotation iskbld.k14s.io/images
):kubectl version
)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.
The text was updated successfully, but these errors were encountered: