You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#638 added the ip and rack fields to nodeStatuses. However this information is not correctly refreshed when a pod is deleted and recreated: the pod IP might change, but the status keeps returning the old IP.
I think this is because I made the changes inside of the if force || nodeStatus.HostID == "" { ... } block. It's probably just a matter of moving them a couple of lines below.
On a side note, it would also be useful to have the CQL port alongside the IP, we can use the opportunity to add it (unless there is a reasonably easy way to infer it from the DC spec).
The text was updated successfully, but these errors were encountered:
On a side note, it would also be useful to have the CQL port alongside the IP, we can use the opportunity to add it (unless there is a reasonably easy way to infer it from the DC spec).
We don't allow changing CQL port at the moment in cass-operator, that work would be relevant to ticket: #242 and requires changes in the port definition codes, which are hardcoded everywhere, like:
So that would be a PR of it's own, requiring design how all the port definitions can be modified, tested, wired to the mgmt-api and supported there also (I'm not sure how much mgmt-api even supports these).
olim7t
added a commit
to olim7t/cass-operator
that referenced
this issue
May 13, 2024
#638 added the
ip
andrack
fields tonodeStatuses
. However this information is not correctly refreshed when a pod is deleted and recreated: the pod IP might change, but the status keeps returning the old IP.I think this is because I made the changes inside of the
if force || nodeStatus.HostID == "" { ... }
block. It's probably just a matter of moving them a couple of lines below.On a side note, it would also be useful to have the CQL port alongside the IP, we can use the opportunity to add it (unless there is a reasonably easy way to infer it from the DC spec).
The text was updated successfully, but these errors were encountered: