feat: deprecate cassandra compatibility #617
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Running the controller with cassandra has caused all sorts of pains for
users.
We already don't provide any tooling and documentation around
running ingress controller with kong and cassandra.
Helm chart removed easy cassandra mode a while ago, this change emits a
warning. In a future version, the controller will not startup if kong is
running with cassandra as it's data-store.
Based on the current statistics, there is a very small group of
users that will be affected by this change.