Inspr daemon doesn't work with more than a replica in kubernetes

[nicholaspcr]

Is your feature request related to a problem? Please describe.
Since the daemon works with a tree structure in memory, when deploying more than a replica there will be conflict between the states of each instance. Also if the pod fails for any reason the memory of the pod could be lost and the tree structure gone.

Describe the solution you'd like
Implement the tree Interface but interacting with a database

Describe alternatives you've considered
Any database will solve the problem, SQL, NoSQL or even something like Redis. This would have an implication on the helm chart since it requires the database/store to exist.

Additional context
Add any other context or screenshots about the feature request here.

[brenordr]

I like this approach. I wonder if would be better Redis or a SQL or even a NoSQL database. In general I would advocate to use the most common.

[brenordr]

@LucasStarlingdePaulaSalles Let's discuss our options by the next grooming session

[brenordr]

@nicholaspcr Thank you for the feedback 👍 :)

[nicholaspcr]

Hey, if you guys decide on what to use might be worth it to write it down here. I'm having two weeks of free time and might be able to contribute to the project

[brenordr]

@nicholaspcr I'll discuss with @LucasStarlingdePaulaSalles tomorrow and move the priority up.
I believe a simple SQL might be the best solution since cloud providers usually have it and it will require one less dependency to install into the cluster. But we need to weight a bit more

[ptcar2009]

@brenordr @nicholaspcr , don't you think it might be good to store those things in an ETCD like database?
And if so, how do you feel about my previous proposal of the dApps being based on k8s CRDs?

[nicholaspcr]

Personally I think both are a pretty good idea, wasn't familiarized with etcd but seems to fit the use case

[brenordr]

@brenordr @nicholaspcr , don't you think it might be good to store those things in an ETCD like database? And if so, how do you feel about my previous proposal of the dApps being based on k8s CRDs?

@ptcar2009 That's actually the direction we are taking now. It's much better to store as CRDs since Kubernetes handle all the storage and sync for us.