kapp flip flops betweek gk scoping and non scoping while using --dangerous-allow-empty-list-of-resources

[praveenrewar]

What steps did you take:
I have a Gitops system where we deploy resources from files using kapp. We just use kapp deploy to deploy and delete resources, and hence we have to use the --dangerous-allow-empty-list-of-resources flag when all files are removed.

$ kapp deploy -a test -f examples/simple-app/config-1.yml
.
.
.
// Deployment and Service Created
$ kapp deploy -a test -f empty-dir --dangerous-allow-empty-list-of-resources
.
.
.
// Deployment and Service deleted. 

What happened:
After the above two commands are run, kapp removes the usedGKs list from the meta ConfigMap. Due to this, the next time kapp deploy is run, kapp doesn't use GK scoping because it thinks that this is an old app which didn't have gk scoping enabled.

What did you expect:
I expected kapp to continue scope the listing to the GKs from the resources I am trying to deploy.

Anything else you would like to add:

Environment:

• kapp version (use kapp --version):
• OS (e.g. from /etc/os-release):
• Kubernetes version (use 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.