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

Expand NodeStatuses with topology information #637

Closed
olim7t opened this issue Apr 19, 2024 · 0 comments · Fixed by #638
Closed

Expand NodeStatuses with topology information #637

olim7t opened this issue Apr 19, 2024 · 0 comments · Fixed by #638
Assignees
Labels
done Issues in the state 'done' enhancement New feature or request

Comments

@olim7t
Copy link
Contributor

olim7t commented Apr 19, 2024

What is missing?

Currently, CassandraDatacenterStatus.NodeStatuses only contains host ids. We could add other information such as the node's IP and rack.

Why is this needed?

This is useful for external tools that need to track the topology of the cluster.

@olim7t olim7t added the enhancement New feature or request label Apr 19, 2024
olim7t added a commit to olim7t/cass-operator that referenced this issue Apr 19, 2024
olim7t added a commit to olim7t/cass-operator that referenced this issue Apr 19, 2024
@adejanovski adejanovski moved this to In Progress in K8ssandra Apr 26, 2024
@adejanovski adejanovski added the in-progress Issues in the state 'in-progress' label Apr 26, 2024
burmanm pushed a commit that referenced this issue May 3, 2024
* Expand nodeStatuses to include IPs and racks (fixes #637)

* Rename IP
@github-project-automation github-project-automation bot moved this from In Progress to Done in K8ssandra May 3, 2024
@adejanovski adejanovski added done Issues in the state 'done' and removed in-progress Issues in the state 'in-progress' labels May 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
done Issues in the state 'done' enhancement New feature or request
Projects
No open projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants