Since the Astarte Kubernetes Operator allows one to have more than one Astarte instance in the same cluster, a natural generalization is to allow multiple Astarte instances to share the same ScyllaDB/Cassandra database.
We should add a way to avoid naming conflicts between keyspaces (as Astarte realms), e.g. two different instances having the test realm (or just having the same astarte keyspace :eyes:).
A possible solution is adding an Astarte instance ID with which to compute the keyspace name, together with the realm name.
This is a meta issue to keep track of changes in different repos:
Since the Astarte Kubernetes Operator allows one to have more than one Astarte instance in the same cluster, a natural generalization is to allow multiple Astarte instances to share the same ScyllaDB/Cassandra database. We should add a way to avoid naming conflicts between keyspaces (as Astarte realms), e.g. two different instances having the
test
realm (or just having the sameastarte
keyspace :eyes:). A possible solution is adding an Astarte instance ID with which to compute the keyspace name, together with the realm name.This is a meta issue to keep track of changes in different repos: