Deploy compressed graph in production kubernetes node
Currently, the production compressed graph is deployed on a static node (granet.i.s.o). We deployed a new graph compressed instance (with the same dataset as granet's) on rancher-node-metal05 only exposed through the webapp-postgresql webapp instance [1]
The plan is to reuse that graph instance as the main graph instance.
We can switch over the webapp-postgres to reuse granet's compressed graph instance (so we can still later on compare results if need be).
Requirements: Granet will remain as-is for the time being.
Plan:
-
swh/infra/ci-cd/swh-charts!494 (merged): Switch to kube's graph compressed instance on services (web, provenance, vault) -
Tag in grafana -
Checks -
Nginx ingress controller: https://grafana.softwareheritage.org/goto/ZcxeYkZHk?orgId=1 -
Compute Resources workload: https://grafana.softwareheritage.org/goto/xyFzPzWNk?orgId=1 -
webapp web-archive api endpoint responds and use the new instance: https://archive.softwareheritage.org/api/1/graph/ -
webapp configuration ok -
provenance configuration ok -
vault configuration? It's actually not using the graph... cookers are -
staging: Fix issue on graph/cookers configuration which were mixed up regarding graph configuration -
webapp web-postgresql api endpoint responds and use granet's instance: https://webapp-postgresql.internal.softwareheritage.org/api/1/graph
-
[1] #5448 (closed)
Edited by Antoine R. Dumont