Change Details

- [x] (vse) create a dedicated repository sysadm-environment/k8s-clusters-config:argo-workflows:/poc-argoworkflow (repo:branch:/directory) - [x] (vse) Publish workflow code in ^ directory: "/workflows" [1] - [x] (vse) Deployment doc on argoWorkflow - [x] (ath) Deployment doc on argoCD - [x] (ath) Publish argocd deployment code related to graphql in sysadm-environment/k8s-clusters-config:argocd:/ - [x] (ard) Deploy graphql locally (using minikube as cluster) - [x] Create dockerhub image softwareheritage/graphql:latest - [x] Deploy it from the swh-charts/swh-graphql helm chart - [x] (ard) Deploy staging kubernetes cluster - [x] Iinventory planification on new nodes and ip - [x] D8152: Prepare puppet manifest to add correct role to new cluster nodes - [x] D8155: Prepare terraform manifest for cluster and nodes creation - [x] Deploy new graphql rancher cluster ^ - [x] (ard) Deploy graphql on the cluster - [x] Manually Deploy graphql from the swh-charts/swh-graphql helm chart - [x] D8159: Expose graphql instance through reverse proxy to one cluster member - [x] 703bd22: Fix with varnish configuration so the graphql application is reached [2] - [x] T4135#88666: Fight with graphql-worker{1,2} so they properly register on the cluster rancher - [x] (ard/ath) T4413 Deploy argocd on admin vlan - [x] (ard/ath) Decomission cluster-graphql to the benefit of cluster-graphql3 - [x] Register graphql-worker{3,2,1} on cluster-graphql3 - [x] Unregister graphql-worker0 from cluster-graphql (and clean up docker leftovers) - [x] Register graphql-worker0 to cluster-graphql3 - [x] Destroy "cluster-graphql" (terraform) - [x] rSPSITE0921c2b: Remove http basic auth currently configured which does not work [4] - [ ] Install load-balancer to access the graphql backend instead of a hard-coded member of the ingress - [ ] ...Pause... - [ ] Deploy argoWorkflow - [ ] (ath/ard) Automatize graphql deployment through ci/cd - [ ] Update manually values-versions.yaml (push) - [ ] Trigger deployment by argocd - [ ] Update values-versions.yaml through CI with argo workflow (manual trigger) - [ ] Monitoring / Alerting to define (thanos federation) - [ ] Metrics / Dashboards - [ ] Update the documentation [1] rSKCONFf89d3a7a6bc43290829b62cf139ebb54f31a1873 [2] https://graphql.staging.swh.network/ [3] https://argo-worker01.internal.admin.swh.network/ [4] The main page is served ok (with the proper creds). But after that, the actual queries to the backend are failing to fetch the data through POST without authentication (so pretty much graphql is useless with that http auth). Currently, puppet is deactivated on rp0.staging with a hot-patched varnish to deactivate http auth for graphql.

- [x] (vse) create a dedicated repository sysadm-environment/k8s-clusters-config:argo-workflows:/poc-argoworkflow (repo:branch:/directory) - [x] (vse) Publish workflow code in ^ directory: "/workflows" [1] - [x] (vse) Deployment doc on argoWorkflow - [x] (ath) Deployment doc on argoCD - [x] (ath) Publish argocd deployment code related to graphql in sysadm-environment/k8s-clusters-config:argocd:/ - [x] (ard) Deploy graphql locally (using minikube as cluster) - [x] Create dockerhub image softwareheritage/graphql:latest - [x] Deploy it from the swh-charts/swh-graphql helm chart - [x] (ard) Deploy staging kubernetes cluster - [x] Iinventory planification on new nodes and ip - [x] D8152: Prepare puppet manifest to add correct role to new cluster nodes - [x] D8155: Prepare terraform manifest for cluster and nodes creation - [x] Deploy new graphql rancher cluster ^ - [x] (ard) Deploy graphql on the cluster - [x] Manually Deploy graphql from the swh-charts/swh-graphql helm chart - [x] D8159: Expose graphql instance through reverse proxy to one cluster member - [x] 703bd22: Fix with varnish configuration so the graphql application is reached [2] - [x] T4135#88666: Fight with graphql-worker{1,2} so they properly register on the cluster rancher - [x] (ard/ath) T4413 Deploy argocd on admin vlan - [x] (ard/ath) Decomission cluster-graphql to the benefit of cluster-graphql3 - [x] Register graphql-worker{3,2,1} on cluster-graphql3 - [x] Unregister graphql-worker0 from cluster-graphql (and clean up docker leftovers) - [x] Register graphql-worker0 to cluster-graphql3 - [x] Destroy "cluster-graphql" (terraform) - [x] rSPSITE0921c2b: Remove http basic auth currently configured which does not work [4] - [ ] ~~Install load-balancer to access the graphql backend instead of a hard-coded member of the ingress~~ (implementation needs to be determined first) - [ ] Monitoring / Alerting: Add a puppet icinga check to raise if the service is down - [ ] D8423: Update the documentation with new service url [1] rSKCONFf89d3a7a6bc43290829b62cf139ebb54f31a1873 [2] https://graphql.staging.swh.network/ [3] https://argo-worker01.internal.admin.swh.network/ [4] The main page is served ok (with the proper creds). But after that, the actual queries to the backend are failing to fetch the data through POST without authentication (so pretty much graphql is useless with that http auth). Currently, puppet is deactivated on rp0.staging with a hot-patched varnish to deactivate http auth for graphql.

- [x] (vse) create a dedicated repository sysadm-environment/k8s-clusters-config:argo-workflows:/poc-argoworkflow (repo:branch:/directory) - [x] (vse) Publish workflow code in ^ directory: "/workflows" [1] - [x] (vse) Deployment doc on argoWorkflow - [x] (ath) Deployment doc on argoCD - [x] (ath) Publish argocd deployment code related to graphql in sysadm-environment/k8s-clusters-config:argocd:/ - [x] (ard) Deploy graphql locally (using minikube as cluster) - [x] Create dockerhub image softwareheritage/graphql:latest - [x] Deploy it from the swh-charts/swh-graphql helm chart - [x] (ard) Deploy staging kubernetes cluster - [x] Iinventory planification on new nodes and ip - [x] D8152: Prepare puppet manifest to add correct role to new cluster nodes - [x] D8155: Prepare terraform manifest for cluster and nodes creation - [x] Deploy new graphql rancher cluster ^ - [x] (ard) Deploy graphql on the cluster - [x] Manually Deploy graphql from the swh-charts/swh-graphql helm chart - [x] D8159: Expose graphql instance through reverse proxy to one cluster member - [x] 703bd22: Fix with varnish configuration so the graphql application is reached [2] - [x] T4135#88666: Fight with graphql-worker{1,2} so they properly register on the cluster rancher - [x] (ard/ath) T4413 Deploy argocd on admin vlan - [x] (ard/ath) Decomission cluster-graphql to the benefit of cluster-graphql3 - [x] Register graphql-worker{3,2,1} on cluster-graphql3 - [x] Unregister graphql-worker0 from cluster-graphql (and clean up docker leftovers) - [x] Register graphql-worker0 to cluster-graphql3 - [x] Destroy "cluster-graphql" (terraform) - [x] rSPSITE0921c2b: Remove http basic auth currently configured which does not work [4] - [ ] ~~Install load-balancer to access the graphql backend instead of a hard-coded member of the ingress - [ ] ...Pause... - [ ] Deploy argoWorkflow - [ ] (ath/ard) Automatize graphql deployment through ci/cd - [ ] Update manually values-versions.yaml (push) - [ ] Trigger deployment by argocd - [ ] Update values-versions.yaml through CI with argo workflow (manual trigger) - [ ] Monitoring / Alerting to define (thanos federation~~ (implementation needs to be determined first) - [ ] Metrics / Dashboardsonitoring / Alerting: Add a puppet icinga check to raise if the service is down - [ ] D8423: Update the documentationn with new service url [1] rSKCONFf89d3a7a6bc43290829b62cf139ebb54f31a1873 [2] https://graphql.staging.swh.network/ [3] https://argo-worker01.internal.admin.swh.network/ [4] The main page is served ok (with the proper creds). But after that, the actual queries to the backend are failing to fetch the data through POST without authentication (so pretty much graphql is useless with that http auth). Currently, puppet is deactivated on rp0.staging with a hot-patched varnish to deactivate http auth for graphql.