etcdvoter after upgrade from 1.25.14 rke2r1 to 1.26.12

[therus000]

etcdvoter after upgrade from 1.25.14 rke2r1 to 1.26.12
i tried to update my cluster from 3 nodes (controlplan).
everything update norm until i updated the firs node
i got status on everynode etcdvoter
the version that i update from 1.25.14 rke2r1
the version that i updated to 1.26.12

[brandond]

Yes, we added a status condition for etcd cluster members. It will be true if the node is a voting member of the cluster. If not, the reason and message will describe why.

Is there a problem?

[therus000]

is that mean that is this status normal?

[brandond]

Yes.

[therus000]

Thank you so much

[bashar-alasmar]

Hey mate, why it shows as a warning ?

[brandond]

That's not a warning, its just a status condition. What makes you think it's a warning?

[bashar-alasmar]

That's not a warning, its just a status condition. What makes you think it's a warning?

Thanks for your reply, in Lens which is visual application for Kubernetes(dashboard , metric ..etc)
It shows in the cluster tab in lens as a warning, however its ready and healthy when i checked

[brandond]

Then Lens is making incorrect assumptions about the status condition. See the discussion at longhorn/longhorn#7290 (comment)