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.

Sign up for GitHub

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

Jump to bottom

Allow us to specify a minimum compatibility version in the cluster config #1567

Closed
RubenKelevra opened this issue Feb 8, 2022 · 1 comment
Closed

Allow us to specify a minimum compatibility version in the cluster config #1567

RubenKelevra opened this issue Feb 8, 2022 · 1 comment
Labels
need/triage Needs initial labeling and prioritization

Comments

@RubenKelevra
Copy link
Collaborator

Describe the feature you are proposing

Currently, there seems to be no way to specify a minimum compatibility version in the cluster config, which leads to older cluster-versions to connect to my collab cluster.

This isn't handled very gracefully by the ipfs-cluster-ctl status page for example #1566

It would be nice to block older cluster versions from connecting, having the cluster daemon just exit if it's blocked from connecting to all nodes specified in the cluster config (at least going forward).

This would allow the admins of the server to see that an error is happening, as the daemon isn't running.
@RubenKelevra RubenKelevra added the need/triage Needs initial labeling and prioritization label Feb 8, 2022
@RubenKelevra
Copy link
Collaborator Author

I feel like this is now obsolete, as the 1.0 version broke capability with older versions. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
need/triage Needs initial labeling and prioritization
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@RubenKelevra