Switch to K8s eLife cluster
-
- recreate server-ingress (k8s.kotahi.cloud -> elife.kotahi.cloud) -
- reswitch DNS cname record elife.kotahi.cloud from EC2 LB to EKS LB -
- update ORCID_CLIENT_ID/SECRET in orcid-secret.yaml and recreate it -
- update PUBLIC_CLIENT_HOST in env-configmap.yaml and recreate it -
- deploy k8s cluster in http://ci.kotahi.cloud/job/k8s-kotahi-deploy (3 deploys: helm del, helm install, helm upgrade) -
- check host elife.kotahi.cloud -
- stop Kotahi stack on elife-kotahi-prod-server EC2 instance -
Testing of all userjourneys on eLife after switching to k8s