-
Task
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
False
-
None
-
False
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
Steps:
[stg-saas][ops] Update sphinx environment with the missing env var added in 2.13 (SECRET_KEY_BASE)[stg-saas][ops] Schedule Sphinx StatefulSet pods into a dedicated node to avoid memory consumption and scheduling issues- [stg-saas][system] Test sphinx indexation and search works properly in staging
- [pro-saas][ops] Progress all changes performed in stg-saas to pro-saas
- [pro-saas][ops] Deploy System custom resource to pro-saas. Set the system-sidekiq and system-app to 0 replicas so only sphinx pod is running. Deploy sphinx prometheus alerts.
- [pro-saas][ops] Expose sphinx server to be reachable from the legacy environment. Can be exposed either through the mt-ingress (envoy) or by adding a Load Balancer to the sphinx statefulset
- [pro-legacy][ops/system] Change system configuration in the legacy platform to point to sphinx in the pro-saas OCP cluster
- is related to
-
THREESCALE-3686 System SaaS migration to OCP
- To Develop