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

Remove unsupported KV store options from configuration and CLI help #3918

Open
kolesnikovae opened this issue Feb 14, 2025 · 1 comment
Open
Labels
🧹 cleanup Important, but often overlooked. Great first issues documentation Improvements or additions to documentation type/docs Improvements for doc docs. Used by Docs team for project management

Comments

@kolesnikovae
Copy link
Collaborator

Currently, only the memberlist implementation of KV storage (used by ring) is supported. However, the configuration specification and CLI help messages also include other types (such as consul, etcd, etc.). We should either ensure that these backends are supported or clean up our documentation. I'm inclined toward the former.

@kolesnikovae kolesnikovae added documentation Improvements or additions to documentation type/docs Improvements for doc docs. Used by Docs team for project management 🧹 cleanup Important, but often overlooked. Great first issues labels Feb 14, 2025
@derek-cadzow
Copy link

@kolesnikovae, it looks like this needs a technical decision before we know whether there's a documentation issue or not. So until it's determined whether we're supporting these backends or updating the documentation, we can't say this is a documentation project. Right now, it doesn't seem we can do anything until that decision is made. Who has the action to make that decision?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🧹 cleanup Important, but often overlooked. Great first issues documentation Improvements or additions to documentation type/docs Improvements for doc docs. Used by Docs team for project management
Projects
None yet
Development

No branches or pull requests

2 participants