search

HCL-TECH-SOFTWARE / connections-automation

Deployment and upgrade automation scripts for HCL Connections 7.0 based on Ansible
Apache License 2.0
17 stars 32 forks source link

Scaling pods on environments with more than 3 nodes #216

Open stoeps13 opened 2 years ago

stoeps13 commented 2 years ago

Hi, the script https://github.com/HCL-TECH-SOFTWARE/connections-automation/blob/8521ea7754c4cadf83e6e1111ab2069331414be0/roles/hcl/component-pack/tasks/scale_component_pack.yml#L5 scales all pods on the number of nodes configured in the Kubernetes cluster, so when you have more than three nodes, it scales to 4, 5, ... pods per deployment.

The persistent volume script always creates hard coded 3 PV independent of the used worker nodes. So all pods which are larger than 3 will write data into non-persistent storage and will lose data when the pod gets rescheduled or when it fails / gets deleted.

So PV creation should also be dependent on the worker node count, or the scale command should stop at three, but I would prefer getting as many PV as Pods!

This affects:

Regards Christoph

sabrina-yee commented 2 years ago

Thanks for the suggestion @stoeps13, we've created an internal ticket for this to work on both the Ansible scripting front and the product chart to create PV / PVC.