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

is it desired to mark Ready even if errors happened? #183

Closed
yuxiangqian opened this issue Mar 6, 2020 · 1 comment · Fixed by #184
Closed

is it desired to mark Ready even if errors happened? #183

yuxiangqian opened this issue Mar 6, 2020 · 1 comment · Fixed by #184

Comments

@yuxiangqian
Copy link

introduced in:
#180

At the following line, it seems the controller will ONLY mark the application to be "ComponentsReady" when counts ready == expected AND there is some error? Is it desired?
https://github.com/kubernetes-sigs/application/blob/master/controllers/application_controller.go#L99

@nan-yu
Copy link
Contributor

nan-yu commented Mar 6, 2020

@yuxiangqian Thanks for catching this! The whole point of #180 is to NOT mark aggregated condition ready when errors happen. It is a dummy typo.
We will consider adding more test cases with mock errors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants