We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This is blocked on #27
We should have the ability for one centralized process to manage the key rotation, so that it can be done in a gradual manner.
The alternative would be to have some sort of leader election to figure out which pod is managing key rotation.
We may want to support both models, given that different consumers may have different hosting schemes and availability requirements.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
This is blocked on #27
We should have the ability for one centralized process to manage the key rotation, so that it can be done in a gradual manner.
The alternative would be to have some sort of leader election to figure out which pod is managing key rotation.
We may want to support both models, given that different consumers may have different hosting schemes and availability requirements.
The text was updated successfully, but these errors were encountered: