Rendre le service scalable à chaud

[rhanka]

Pour rendre le service plus performant sans faire exploser les cout d'hébergement Scaleway, une migration vers kubernetes est nécessaire et prendra plusieurs étapes

Step 1 - Local deployment

• [x] redis
• [x] elasticsearch + restore (basic)
• [x] backend (basic, no proofs data)
• [x] frontend (built mode, no dev mode)
• [x] ingress

Step 2 - Scaleway deployment

• [ ] redis
• [ ] elasticsearch + restore (basic)
• [ ] backend (basic, no proofs data)
• [ ] frontend (built mode, no dev mode)
• [ ] ingress
• [ ] elasticsearch + scalability (from volume duplication to speed-up scaling)
• [ ] backend: glusterfs for link jobs sharing and full backend scalability
• [ ] full scalability tuning (+perf tests)
• [ ] backend : backup / restore proofs (k8s jobs)
• [ ] dataprep standalone update (from dataprep repo)
• [ ] backend standalone update (from dataprep repo)
• [ ] frontend standalone update (from deces-ui repo)
• [ ] disaster recovery / full redeployment