Hello,
I am trying to deploy frappe on a EKS cluster, all of the pods are in running or completed state.
The deployment is using helm, persistence volume used is gp2, database used is RDS, to access the frappe i created the ALB ingress using seperate manifest.
Although Everything in eks related to frappe is running, i can’t access the frappe from my browser.
But the target in target_group associated with alb is is unhealthy.
Below are the resources running:
C:\Users\toufi\erpnext>k get all -n frappe
NAME READY STATUS RESTARTS AGE
pod/frappe-erpnext-conf-bench-20241224174245-dt4np 0/1 Completed 0 103m
pod/frappe-erpnext-gunicorn-774b7c6bd6-zndlj 1/1 Running 0 103m
pod/frappe-erpnext-new-site-20241224174245-td8zp 0/1 Completed 0 103m
pod/frappe-erpnext-nginx-6d98594fc-gqhfq 1/1 Running 0 103m
pod/frappe-erpnext-scheduler-7666b89c5d-wf85t 1/1 Running 0 103m
pod/frappe-erpnext-socketio-66bd5c48d9-9rlhq 1/1 Running 2 (103m ago) 103m
pod/frappe-erpnext-vol-fix-20241224174245-qnx77 0/1 Completed 0 103m
pod/frappe-erpnext-worker-d-77546cdb67-t45wc 1/1 Running 2 (103m ago) 103m
pod/frappe-erpnext-worker-l-7bf47c4958-hp7t6 1/1 Running 2 (103m ago) 103m
pod/frappe-erpnext-worker-s-57cdf68cf6-nv4db 1/1 Running 2 (103m ago) 103m
pod/frappe-redis-cache-master-0 1/1 Running 0 103m
pod/frappe-redis-queue-master-0 1/1 Running 0 103m
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/frappe-erpnext ClusterIP 172.20.181.152 <none> 8080/TCP 103m
service/frappe-erpnext-gunicorn ClusterIP 172.20.101.253 <none> 8000/TCP 103m
service/frappe-erpnext-socketio ClusterIP 172.20.218.20 <none> 9000/TCP 103m
service/frappe-redis-cache-headless ClusterIP None <none> 6379/TCP 103m
service/frappe-redis-cache-master ClusterIP 172.20.174.60 <none> 6379/TCP 103m
service/frappe-redis-queue-headless ClusterIP None <none> 6379/TCP 103m
service/frappe-redis-queue-master ClusterIP 172.20.184.230 <none> 6379/TCP 103m
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/frappe-erpnext-gunicorn 1/1 1 1 103m
deployment.apps/frappe-erpnext-nginx 1/1 1 1 103m
deployment.apps/frappe-erpnext-scheduler 1/1 1 1 103m
deployment.apps/frappe-erpnext-socketio 1/1 1 1 103m
deployment.apps/frappe-erpnext-worker-d 1/1 1 1 103m
deployment.apps/frappe-erpnext-worker-l 1/1 1 1 103m
deployment.apps/frappe-erpnext-worker-s 1/1 1 1 103m
NAME DESIRED CURRENT READY AGE
replicaset.apps/frappe-erpnext-gunicorn-774b7c6bd6 1 1 1 103m
replicaset.apps/frappe-erpnext-nginx-6d98594fc 1 1 1 103m
replicaset.apps/frappe-erpnext-scheduler-7666b89c5d 1 1 1 103m
replicaset.apps/frappe-erpnext-socketio-66bd5c48d9 1 1 1 103m
replicaset.apps/frappe-erpnext-worker-d-77546cdb67 1 1 1 103m
replicaset.apps/frappe-erpnext-worker-l-7bf47c4958 1 1 1 103m
replicaset.apps/frappe-erpnext-worker-s-57cdf68cf6 1 1 1 103m
NAME READY AGE
statefulset.apps/frappe-redis-cache-master 1/1 103m
statefulset.apps/frappe-redis-queue-master 1/1 103m
NAME STATUS COMPLETIONS DURATION AGE
job.batch/frappe-erpnext-conf-bench-20241224174245 Complete 1/1 23s 103m
job.batch/frappe-erpnext-new-site-20241224174245 Complete 1/1 71s 103m
job.batch/frappe-erpnext-vol-fix-20241224174245 Complete 1/1 55s 103m
C:\Users\toufi\erpnext>k get ingress -n frappe
NAME CLASS HOSTS ADDRESS PORTS AGE
frappe-ingress alb * k8s-frappe-frappein-************.ap-south-1.elb.amazonaws.com 80 5d2h
C:\Users\toufi\erpnext>helm list -n frappe
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
frappe frappe 1 2024-12-24 17:42:45.4818249 +0530 IST deployed erpnext-7.0.146 v15.45.5
There is no indication of errors in pod logs that i know of, I am not sure what the issue is.
If any info needed please let me know, Thankyou.