cluster-lock.json file limitations on k8s

[0xDones]

🎯 Problem to be solved

Is there another way to handle the cluster-lock.json file? K8s secrets have a 1MB size limitation and with 1000 validators in the cluster-lock file, the file will be 2MB in size, preventing the secret from being created.

🛠️ Proposed solution

Can't Charon fetch the cluster-lock.json file in a similar way DKG does for the definition file?

🧪 Tests

• Test steps or automation scripts are provided
• The chart is deployed to the test environment successfully

👐 Additional acceptance criteria

• The helm chart is published to artifactory
• The chart docs are updated
• The chart is released to live environments (if applicable)

❌ Out of Scope

[aly-obol]

@refl3ction, thanks for bringing this constraint to the discussion. Charon does not have an option to load the cluster-lock from a URI. Still, I am discussing the visibility of adding this option with the team.

Meanwhile, we did a workaround to run our test clusters with a large cluster-lock file by loading it from a secure s3 bucket or vault using an init-container: https://github.com/ObolNetwork/charon-k8s-distributed-validator-cluster/blob/241e27bf7c3d96cc3d22e63108084aa3971885c0/templates/charon-perf.yaml#L51