Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kapp creates state configmap on --diff-run #432

Closed
schmurfy opened this issue Feb 14, 2022 · 6 comments · Fixed by #454
Closed

kapp creates state configmap on --diff-run #432

schmurfy opened this issue Feb 14, 2022 · 6 comments · Fixed by #454
Assignees
Labels
carvel accepted This issue should be considered for future work and that the triage process has been completed carvel triage This issue has not yet been reviewed for validity duplicate This issue is already captured by another issue enhancement This issue is a feature request

Comments

@schmurfy
Copy link

What steps did you take:
kapp deploy -a myapp -f . --diff-run

What happened:
kapp shows the diff but created an empty configmap for this app, when running kapp list afterwards the app is shown in the list with "-" as namespace, an inspect list nothing, as it should

What did you expect:
nothing changed on the cluster

Anything else you would like to add:
[Additional information that will assist in solving the issue.]

Environment:

  • kapp version (use kapp --version): kapp version 0.42.0 (I checked but no changes on this appear on the changelogs for the following releases)
  • OS (e.g. from /etc/os-release): osx, linux
  • Kubernetes version (use kubectl version)
lient Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.3", GitCommit:"1e11e4a2108024935ecfcb2912226cedeafd99df", GitTreeState:"clean", BuildDate:"2020-10-14T18:49:28Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"20+", GitVersion:"v1.20.12-gke.1500", GitCommit:"d32c0db9a3ccd0ac73b0b3abd0532505217b376e", GitTreeState:"clean", BuildDate:"2021-11-17T09:30:02Z", GoVersion:"go1.15.15b5", Compiler:"gc", Platform:"linux/amd64"}

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.

@schmurfy schmurfy added bug This issue describes a defect or unexpected behavior carvel triage This issue has not yet been reviewed for validity labels Feb 14, 2022
@cppforlife cppforlife changed the title kapp creates configmaps on --diff-run kapp creates state configmap on --diff-run Feb 14, 2022
@100mik
Copy link
Contributor

100mik commented Feb 15, 2022

Looks like this issue is also being tracked in this one #23

@rohitagg2020
Copy link
Contributor

@rohitagg2020 Please check: When diff-run is performed against the labeled app, we don't create configmap. Can we convert recorded app to labeled app and do the diff-run.

@renuy renuy added the duplicate This issue is already captured by another issue label Feb 15, 2022
@schmurfy
Copy link
Author

@rohitagg2020 What are labeled apps and recorded apps ?

@cppforlife
Copy link
Contributor

cppforlife commented Feb 15, 2022

rohit is referring to using -a label:x=y (labeled) instead of -a app-name (recorded). currently only recorded apps get "created" even for --diff-run. (*note: i always recommend using recorded apps in 99% cases. labeled apps were introduced as an advanced/specialized option, especially useful for browsing cluster e.g. kapp inspect -a label:)

i think your ask is totally reasonable and we should address it, since if the app doesnt exist its only fair it should not get created with --diff-run (current behaviour was intentionally left for implementation simplicity, so not a bug, but it's probably time to improve it).

@cppforlife cppforlife added enhancement This issue is a feature request and removed bug This issue describes a defect or unexpected behavior labels Feb 15, 2022
@rohitagg2020
Copy link
Contributor

@schmurfy I apologize for being ambiguous. It was a note to self.

@renuy renuy added the carvel accepted This issue should be considered for future work and that the triage process has been completed label Mar 21, 2022
@cppforlife cppforlife removed the carvel triage This issue has not yet been reviewed for validity label Mar 22, 2022
@sethiyash sethiyash linked a pull request May 6, 2022 that will close this issue
@renuy
Copy link
Contributor

renuy commented May 31, 2022

fix available as part of v0.48.0

@github-actions github-actions bot added the carvel triage This issue has not yet been reviewed for validity label May 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
carvel accepted This issue should be considered for future work and that the triage process has been completed carvel triage This issue has not yet been reviewed for validity duplicate This issue is already captured by another issue enhancement This issue is a feature request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants