Node getting ready is reported as an error

[eddycharly]

Describe the bug The node getting ready is reported as an error.

[PrasadG193]

Isn't that expected? If Node is not ready, then we should get informed, right?

[eddycharly]

In this case the node is ready, i don’t think it should be considered an error

[PrasadG193]

I can see in the screenshot the status is NotReady. It might have happened that the node came back to Ready status?

[eddycharly]

In the screenshot the status is NodeReady not NotReady. Where do you see NotReady ?

[PrasadG193]

I am really sorry. It is NodeReady, I mistakenly ready it as NotReady. I am on smaller screen so coudn't find the difference :man_facepalming:. Thanks for reporting. This is not the expected behaviour. We have dedicated filter to extract node status from the event info. There must be something going wrong there

[codenio]

I would like to work on this. If someone had started already, kindly let me know.

[coolpalani]

@codenio

I tried to setup from develop branch and tag v0.10.0, I didn't get any alert while node isn't NotReady or recover from NotReady to Ready state.

- name: node namespaces: include: - all ignore: - events: - create - update - delete - error updateSetting: includeDiff: true fields: - status.conditions[*].type

Also if we cordon/uncordon, evict we should get notifications. I didn't get any details in the documents.

[codenio]

@coolpalani Is this issue remains unresolved.?

[codenio]

is this unresolved..?

[clementnuss]

I experience the same behavior, has anyone being able to solve this?

[pkosiec]

Hi all, From what I could see on the old screenshot, the NodeReady event wasn't reported as error (green border was used for "create/info" events).

In recent Botkube versions (1.0+) You can exclude notifications based on reason, message and other patterns. Please see the docs here: https://docs.botkube.io/configuration/source/kubernetes. If such event is reported as error in the latest Botkube 1.5.0 version, please create another issue. Thank you!