1. using deployment instead of statefulset
In this helm charts, statefulset(sts) is used for server node deployment of the application. Can we use "Deployment" for this?
The reason for asking this is each STS pod/instance needs a separate PVC. This works fine. Reducing the number of replicas in a StatefulSet can lead to unused PVCs, as each StatefulSet Pod is associated with a unique PVC. If a Pod is scaled down or removed, its corresponding PVC remains, which can result in unused but potentially important data being left behind.
2. rolling update
Currently I see the pod is recreated instead of rolling updated. This results in downtime. Can rolling update be a solution here?
Hello DKron team,
I have two questions.
1. using deployment instead of statefulset In this helm charts, statefulset(sts) is used for server node deployment of the application. Can we use "Deployment" for this?
The reason for asking this is each STS pod/instance needs a separate PVC. This works fine. Reducing the number of replicas in a StatefulSet can lead to unused PVCs, as each StatefulSet Pod is associated with a unique PVC. If a Pod is scaled down or removed, its corresponding PVC remains, which can result in unused but potentially important data being left behind.
2. rolling update Currently I see the pod is recreated instead of rolling updated. This results in downtime. Can rolling update be a solution here?
-- Raghav