BUG: CockroachDB stops install process

[saashqdev]

Sealos Version

v5.0.0-beta5

How to reproduce the bug?

curl -sfL https://raw.githubusercontent.com/labring/sealos/v5.0.0-beta5/scripts/cloud/install.sh -o /tmp/install.sh && bash /tmp/install.sh \
--cloud-domain=<your_domain> \
--cert-path=<your_crt> \
--key-path=<your_key>

What is the expected behavior?

Full install

What do you see instead?

...
2024-07-05T19:59:06 info Executing pipeline MirrorRegistry in InstallProcessor.
2024-07-05T19:59:06 info Executing UpgradeIfNeed Pipeline in InstallProcessor
namespace/sealos-system created
namespace/sealos created
customresourcedefinition.apiextensions.k8s.io/notifications.notification.sealos.io created
no mongodb uri found, create mongodb and gen mongodb uri
waiting for mongodb secret generated
waiting for mongodb ready ...mongodb secret has been generated successfully.
no cockroachdb uri found, create cockroachdb and gen cockroachdb uri
cockroachdb statefulset is created.
waiting for cockroachdb ready    Error: signal: killed
waiting for cockroachdb ready ...

Operating environment

- Sealos version: v5.0.0-beta5
- Docker version: v20.10.7
- Kubernetes version: v1.25.0
- Operating system: Ubuntu 24.04
- Runtime environment: 3 x 4gb / 2 cpu / 40GB server (Hetzner - CX22's)
- Cluster size: 1 master, 2 nodes
- Additional information:

Additional information

Install just stops with trying to start CockroachDB in the cluster. Eventually signal gets killed. Maybe not enough resources? There was an older issue like this (#4704). Just wondering if they were able to solve it. Cheers, Dave

[saashqdev]

Just added more resources. Increased the master node to 8gb, 4core, 120gb.