-
Notifications
You must be signed in to change notification settings - Fork 110
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
Comments
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? |
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. |
…ed api (#160) Signed-off-by: Garrett Cheadle <gcheadle@vmware.com>
…ed api (#160) Signed-off-by: Garrett Cheadle <gcheadle@vmware.com>
…ed api (#160) Signed-off-by: Garrett Cheadle <gcheadle@vmware.com>
This is available in release v0.36.0 |
Addresses issue carvel-dev/kapp#160
Addresses issue carvel-dev/kapp#160
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).
The text was updated successfully, but these errors were encountered: