-
Notifications
You must be signed in to change notification settings - Fork 20
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
fix(controllers): object not committed properly #550
Conversation
f244b5e
to
1a25287
Compare
@byashimov yes, you were right! 😆 |
Hey. You mean the RUNNING status? I'm fixing it right now. But it is a hard one. |
@byashimov yes, but i only see the issue for KafkaACL. |
@tkaesserfm it is actually there for every kind. |
Ah i see, i was talking "Status Conditions" so different thing but the symptom seems the same. |
6db78a4
to
ccc4ad1
Compare
Hey @tkaesserfm
The only thing is that I have narrowed down the list of reasons. It's good to have a verbose state machine, but unfortunately our controllers have just one That means that every return statement with an error has to have a "set a reason" line behind.
Regarding to missing events: turns out that by default (and actually recommended way) events might be dropped out when there are too much of them. So events are unreliable. Thankfully, you use conditions. Can you confirm this works for you? |
b5207b5
to
33ce964
Compare
33ce964
to
aac610b
Compare
aac610b
to
8bae46c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This PR: