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

Auto-fallback provider for Kerberos Vault #66

Open
cedricve opened this issue Nov 2, 2023 · 0 comments
Open

Auto-fallback provider for Kerberos Vault #66

cedricve opened this issue Nov 2, 2023 · 0 comments

Comments

@cedricve
Copy link
Member

cedricve commented Nov 2, 2023

Currently it's only possible to store in a single provider, however:

  1. a provider might become unavailable for a long time,
  2. there is a need to load balance providers (different clouds, different datacenters, hybrid storage (edge/cloud storage)
  3. regionality: depending on a header defined in Kerberos Agent or Kerberos Factory a recording might be stored in a specific storage location.

With this feature we will provide a solution for above scenarios, giving another compelling edge to our scalable solution stack.

@cedricve cedricve added this to Roadmap May 28, 2024
@cedricve cedricve moved this to Future in Roadmap May 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Future
Development

No branches or pull requests

1 participant