edit memory, add mongo kubernetes, edit readme and fix init-mongo

Author: rjkoh

deployKubernetes.sh

@@ -4,6 +4,26 @@
 DOCKER_USERNAME="rjkoh"
 TAG="latest"
 
+echo "Applying Kubernetes deployment file for kafka..."
+kubectl apply -f kubernetes/kafka/kafka-deployment.yaml --validate=false
+echo "Deployment for kafka complete."
+echo "----------------------------------------"
+
+echo "Applying Kubernetes deployment file for zookeeper..."
+kubectl apply -f kubernetes/zookeeper/zookeeper-deployment.yaml --validate=false
+echo "Deployment for zookeeper complete."
+echo "----------------------------------------"
+
+echo "Applying Kubernetes deployment file for redis..."
+kubectl apply -f kubernetes/redis/redis-deployment.yaml --validate=false
+echo "Deployment for redis complete."
+echo "----------------------------------------"
+
+echo "Applying Kubernetes deployment file for mongo..."
+kubectl apply -f kubernetes/mongo/mongo-deployment.yaml --validate=false
+echo "Deployment for mongo complete."
+echo "----------------------------------------"
+
 # Lists of services and their corresponding deployment YAML paths
 services=("collaboration-service" "matching-service" "question-service" "user-service")
 
@@ -77,19 +97,4 @@ rm "$K8S_DEPLOYMENT_FILE.bak"
 echo "Deployment for $SERVICE complete."
 echo "----------------------------------------"
 
-echo "Applying Kubernetes deployment file for kafka..."
-kubectl apply -f kubernetes/kafka/kafka-deployment.yaml --validate=false
-echo "Deployment for kafka complete."
-echo "----------------------------------------"
-
-echo "Applying Kubernetes deployment file for zookeeper..."
-kubectl apply -f kubernetes/zookeeper/zookeeper-deployment.yaml --validate=false
-echo "Deployment for zookeeper complete."
-echo "----------------------------------------"
-
-echo "Applying Kubernetes deployment file for redis..."
-kubectl apply -f kubernetes/redis/redis-deployment.yaml --validate=false
-echo "Deployment for redis complete."
-echo "----------------------------------------"
-
 echo "All services deployed successfully."

init-mongo.js

@@ -3,7 +3,7 @@ const resetAllDatabases = true;
 const MONGO_INITDB_ROOT_USERNAME = "admin";
 const MONGO_INITDB_ROOT_PASSWORD = "password";
 const PEERPREP_QUESTION_INITDB_NAME = "peerprepQuestionServiceDB";
-// const PEERPREP_USER_INITDB_NAME = "peerprepUserServiceDB";
+const PEERPREP_USER_INITDB_NAME = "peerprepUserServiceDB";
 // const PEERPREP_COLLAB_INITDB_NAME = "peerprepCollabServiceDB";
 
 db.getSiblingDB("admin").auth(MONGO_INITDB_ROOT_USERNAME, MONGO_INITDB_ROOT_PASSWORD);
@@ -221,7 +221,7 @@ if (isUserDatabaseResetDesired) {
 }
 
 /*---------------USER-SERVICE-DB-INIT----------------*/
-/*const users = [
+const users = [
     {
         "username": "admin",
         "email": "[email protected]",
@@ -248,7 +248,7 @@ users.forEach(user => {
             isAdmin: user.isAdmin
         });
     }
-});*/
+});
 
 /*-----------------------------INDEXING-(OPTIONAL)---------------------------------*/
 

kubernetes/README.md

@@ -12,11 +12,12 @@
 
 3. Build the PeerPrep Docker containers with `docker compose build`
 4. Create the configmap for the nginx api-gateway: run `kubectl create configmap nginx-config --from-file=backend/api-gateway/nginx.conf` at root.
-5. Add your docker username in `deploy.sh` at root.
-6. To deploy on Kubernetes, run `./deploy.sh` at root.
-7. View deployments, pods and HPA. Ensure all services are running. `kubectl get all`
-8. Wait for a few minutes for kubernetes to become fully functional. It is ready when running `kubectl get hpa` does not show any `<unknown>` under `TARGETS`
-9. Load testing: 
+5. Create the configmap for mongo: run `kubectl create configmap init-mongo-script --from-file=init-mongo.js` at root.
+6. Add your docker username in `deploy.sh` at root.
+7. To deploy on Kubernetes, run `./deploy.sh` at root.
+8. View deployments, pods and HPA. Ensure all services are running. `kubectl get all`
+9. Wait for a few minutes for kubernetes to become fully functional. It is ready when running `kubectl get hpa` does not show any `<unknown>` under `TARGETS`
+10. Load testing: 
     * In a separate terminal, run command to carry conduct load testing
     ```
     kubectl run -i --tty load-generator --rm --image=busybox:1.28 --restart=Never -- /bin/sh -c "while sleep 0.01; do wget -q -O- http://<service>.default.svc.cluster.local:<port>/<route>/test; done"
@@ -27,11 +28,12 @@
       3. Matching Service: `http://matching-service.default.svc.cluster.local:3003/api/matchtest`
       4. Collaboration Service: `http://collaboration-service.default.svc.cluster.local:3004/api/collab/test`
     * `Ctrl + C` to stop sending requests
+    * Testing can also be done on our deployed instance, by replacing the address with `52.221.131.145`. For example, `http://52.221.131.145:3001/users/test`. However, this is unlikely to result in any scaling due to Amazon EC2 throttling EC2 API requests for each AWS account on a per-Region basis, hence limiting the load imposed on each service.
 
-10. Monitor autoscaling with `kubectl get hpa <service>-hpa --watch`. This command will watch the HPA in real-time, showing changes in replica counts and metrics. It requires a few minutes for the pods to scale up and down. Replace `<service>` appropriately with:
+11. Monitor autoscaling with `kubectl get hpa <service>-hpa --watch`. This command will watch the HPA in real-time, showing changes in replica counts and metrics. It requires a few minutes for the pods to scale up and down. Replace `<service>` appropriately with:
     * user-service
     * question-service
     * matching-service
     * collaboration-service
 
-11. `Ctrl + C` to exit. To stop and delete to prevent resource wastage: `kubectl delete all --all`
+12. `Ctrl + C` to exit. To stop and delete to prevent resource wastage: `kubectl delete all --all`

kubernetes/backend/matching-service-deployment.yaml

@@ -26,8 +26,8 @@ spec:
             value: peerprep-kafka.default.svc.cluster.local
         resources:
           requests:
-            cpu: "200m"
-            memory: "512Mi"
+            cpu: "100m"
+            memory: "256Mi"
           limits:
             cpu: "500m"
             memory: "1Gi"

kubernetes/backend/user-service-deployment.yaml

@@ -24,8 +24,8 @@ spec:
             value: peerprep-mongodb.default.svc.cluster.local
         resources:
           requests:
-            cpu: "100m"
-            memory: "256Mi"
+            cpu: "300m"
+            memory: "768Mi"
           limits:
             cpu: "500m"
             memory: "1Gi"

kubernetes/mongo/mongo-deployment.yaml

@@ -0,0 +1,59 @@
+apiVersion: apps/v1
+kind: Deployment
+metadata:
+    name: peerprep-mongodb
+spec:
+    replicas: 1
+    selector:
+        matchLabels:
+            app: peerprep-mongodb
+    template:
+        metadata:
+            labels:
+                app: peerprep-mongodb
+        spec:
+            containers:
+                - name: peerprep-mongodb
+                  image: mongo:latest
+                  ports:
+                      - containerPort: 27017
+                  env:
+                      - name: MONGO_INITDB_ROOT_USERNAME
+                        value: "admin"
+                      - name: MONGO_INITDB_ROOT_PASSWORD
+                        value: "password"
+                  volumeMounts:
+                      - name: init-script
+                        mountPath: /docker-entrypoint-initdb.d/init-mongo.js
+                        subPath: init-mongo.js
+            volumes:
+                - name: init-script
+                  configMap:
+                      name: init-mongo-script
+---
+apiVersion: v1
+kind: Service
+metadata:
+    name: peerprep-mongodb
+spec:
+    ports:
+        - port: 27017
+          targetPort: 27017
+    selector:
+        app: peerprep-mongodb
+    type: ClusterIP
+
+---
+apiVersion: v1
+kind: PersistentVolumeClaim
+metadata:
+    name: mongodb-pvc
+spec:
+    accessModes:
+        - ReadWriteOnce
+    resources:
+        requests:
+            storage: 1Gi
+
+---
+