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 should double check that k8s api returns labeled resources #160

Closed
cppforlife opened this issue Nov 12, 2020 · 3 comments
Closed

kapp should double check that k8s api returns labeled resources #160

cppforlife opened this issue Nov 12, 2020 · 3 comments
Assignees
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

Comments

@cppforlife
Copy link
Contributor

currently kapp trusts that k8s api returns resources based on the label query specified. it appears that if aggregated api impl come into play there is no guarantee that they return resources filted by label as requested (antrea for example did not implement label selector).

@cppforlife cppforlife added the enhancement This issue is a feature request label Nov 12, 2020
@danielhelfand
Copy link
Contributor

As a question on this, would the result of this labeled resource check result in an error message to the user? Or is there some other plan for the recovery in this scenario?

@cppforlife
Copy link
Contributor Author

would the result of this labeled resource check result in an error message to the user

if resource is not appropriately labeled, then it would "eliminate" resource from further processing like diffing (== consider that resource as not being there). this would allow kapp to work with aggregated apis that do not behave up to spec.

@cari-lynn cari-lynn linked a pull request Jan 28, 2021 that will close this issue
@aaronshurley aaronshurley added Epic and removed Epic labels Feb 23, 2021
@gcheadle-vmware gcheadle-vmware self-assigned this Feb 23, 2021
@gcheadle-vmware gcheadle-vmware added the carvel accepted This issue should be considered for future work and that the triage process has been completed label Feb 23, 2021
@cari-lynn cari-lynn self-assigned this Feb 24, 2021
gcheadle-vmware pushed a commit that referenced this issue Mar 4, 2021
…ed api (#160)

Signed-off-by: Garrett Cheadle <gcheadle@vmware.com>
gcheadle-vmware pushed a commit that referenced this issue Mar 4, 2021
…ed api (#160)

Signed-off-by: Garrett Cheadle <gcheadle@vmware.com>
gcheadle-vmware pushed a commit that referenced this issue Mar 4, 2021
…ed api (#160)

Signed-off-by: Garrett Cheadle <gcheadle@vmware.com>
@aaronshurley aaronshurley added the in progress Work has begun by a community member or a maintainer; this issue may be included in a future release label Mar 9, 2021
@cari-lynn cari-lynn removed the in progress Work has begun by a community member or a maintainer; this issue may be included in a future release label Mar 10, 2021
@cari-lynn
Copy link
Contributor

This is available in release v0.36.0

danielhelfand added a commit to carvel-dev/kapp-controller that referenced this issue Mar 10, 2021
cppforlife pushed a commit to carvel-dev/kapp-controller that referenced this issue Mar 11, 2021
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 enhancement This issue is a feature request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants