Ability to set namespace for storing kapp meta configmaps

[Praveen Rewar]

Describe the problem/challenge you have
I want to set the namespace for storing the kapp metadata configmaps. Currently this is being done via the default namespace from the kubeconfig or by using the -n flag, but both of them set this for all the resources that are created by the app (unless the resources have a metadata.namespace field specified). This requires me to provide kapp with create/update and delete permissions for configmaps in my namespace. I would like to keep these separate so that I can isolate the rbac resources in a different namespace

Describe the solution you'd like
Add a flag --app-namespace in the kapp commands which can be used to specify the namespace to store the kapp meta configmaps.

Anything else you would like to add:
The --app-namespace flag would take precedence over the -n flag, but if --app-namespace is not specified then kapp would behave in the same fashion as it does now, this will ensure that users who are already using kapp won't be impacted.

---

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.