Blog article
ERPNext Deployment on Kubernetes using Helm: The Complete Step-by-Step Production Guide
This guide deploys ERPNext on any Kubernetes cluster using the official ERPNext Helm chart repo and a standard Ingress + Let's Encrypt TLS (cert-manager) setup.
At a glance
- Written by
- Midocean DevOps Team
- Published
- May 26, 2026
- Reading time
- 8 min read
- Topic
- DevOps
This guide deploys ERPNext on any Kubernetes cluster using the official ERPNext Helm chart repo and a standard Ingress + Let's Encrypt TLS (cert-manager) setup.
0) Prerequisites
Required tools
kubectlconfigured to your clusterhelmv3+
Required cluster capabilities
- A StorageClass that supports RWX (ReadWriteMany) (examples: AWS EFS, Azure Files, NFS, CephFS). Do not use ReadWriteOnce (RWO) storage classes for shared volumes.
1) Install NGINX Ingress Controller (ingress-nginx)
kubectl create namespace ingress-nginx
helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx
helm repo update
helm upgrade --install ingress-nginx ingress-nginx/ingress-nginx -n ingress-nginx
Confirm:
kubectl get pods -n ingress-nginx
kubectl get svc -n ingress-nginx
2) Install cert-manager (for TLS automation)
kubectl create namespace cert-manager
helm repo add jetstack https://charts.jetstack.io
helm repo update
helm upgrade --install cert-manager jetstack/cert-manager -n cert-manager --set installCRDs=true
3) Create a Let’s Encrypt ClusterIssuer
Create a clusterissuer.yaml file with the following content:
apiVersion: cert-manager.io/v1
kind: ClusterIssuer
metadata:
name: letsencrypt-prod
spec:
acme:
email: YOUR_EMAIL
server: https://acme-v02.api.letsencrypt.org/directory
privateKeySecretRef:
name: letsencrypt-prod-account-key
solvers:
- http01:
ingress:
class: nginx
Apply it:
kubectl apply -f clusterissuer.yaml
4) Add ERPNext Helm repo
helm repo add frappe https://helm.erpnext.com
helm repo update
5) Create namespace for ERPNext
export NAMESPACE=erpnext
kubectl create namespace $NAMESPACE
6) Pick an RWX StorageClass
ERPNext needs shared RWX (ReadWriteMany) storage for the shared sites/worker volume. Set your storage class name:
- AWS EFS: efs-sc
- Azure Files: azurefile-csi
- NFS/CephFS: depends on cluster
export RWX_STORAGE_CLASS="YOUR_RWX_STORAGECLASS"
7) Create a minimal values-erpnext.yaml
Create a values-erpnext.yaml file with the following configuration. Replace erp.example.com with your production domain:
persistence:
worker:
enabled: true
storageClass: "${RWX_STORAGE_CLASS}"
accessModes:
- ReadWriteMany
size: 20Gi
ingress:
enabled: true
annotations:
cert-manager.io/cluster-issuer: "letsencrypt-prod"
hosts:
- host: "erp.example.com"
paths:
- path: /
pathType: ImplementationSpecific
tls:
- secretName: erpnext-tls
hosts:
- "erp.example.com"
jobs:
createSite:
enabled: true
siteName: "erp.example.com"
adminPassword: "ChangeThisAdminPassword!"
installApps:
- "erpnext"
dbType: "mariadb"
mariadb-sts:
enabled: true
rootPassword: "ChangeThisDBRootPassword!"
8) Deploy ERPNext with Helm
export RELEASE=frappe-bench
helm upgrade --install $RELEASE frappe/erpnext -n $NAMESPACE -f values-erpnext.yaml
9) Wait for pods and validate
kubectl get pods -n $NAMESPACE -w
kubectl get ingress -n $NAMESPACE
kubectl get certificate -n $NAMESPACE
Once the certificate is successfully issued by Let's Encrypt, open your browser and navigate to: https://erp.example.com
Default login:
- Username: Administrator
- Password: ChangeThisAdminPassword! (from values-erpnext.yaml)