We absolutely love the Kong Ingress Controller. Being able to configure Kong via Kubernetes resources makes our lives so much easier.
But we also leverage the oauth2 plugin, and historically have used Cassandra as our db backend.
I understand the latest version of the KIC no longer supports Cassandra. We’ve heavily invested in Cassandra for other needs, and have Cassandra clusters that span many datacenters. In other projects leveraging Kong (not the KIC), this has allowed us to perform DR moving customers from one data center to another without them having to request another oauth2 token - they don’t even notice (as Cassandra handles the replication of their oauth2 tokens to all our data centers)
To achieve the same level of availability and be able to leverage the KIC we could deploy postgreSQL, but we’d really like to not have to invest in another db technology given our current investments and expertise around Cassandra. Is it possible to run the KIC DB-less - and just have the oauth2 tokens stored in Cassandra? I’ve been reading up on the data and control plane features of Kong but it wasn’t clear to me if this is the direction we should be heading to achieve this or not.