Summary of Changes

Hello @roderik, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a significant improvement to the deployment strategy and health checking of network nodes within a Kubernetes environment. By enabling parallel pod management for validator StatefulSets, it aims to accelerate deployment and scaling. Concurrently, it refines the readiness probe configuration to ensure nodes are genuinely operational by requiring at least one peer connection and increasing the frequency of health checks, leading to more robust and responsive deployments.

Highlights

• Parallel Deployment for Validators: The StatefulSet for validator nodes has been configured to use podManagementPolicy: Parallel. This change allows all pods in the StatefulSet to be created or updated in parallel, rather than sequentially, which can significantly speed up deployment and scaling operations.
• Enhanced Readiness Check Logic: The readiness probe's HTTP GET path has been updated to require a minimum of one peer (minPeers=1) for a node to be considered ready. Previously, it allowed zero peers, which could lead to nodes being marked ready before fully synchronizing or connecting to the network.
• Increased Readiness Probe Frequency: The frequency of the readiness probe checks has been doubled, with periodSeconds reduced from 10 to 5. This ensures that the system detects the readiness status of pods more quickly, allowing for faster reaction to changes in pod health.

Hey there - I've reviewed your changes - here's some feedback:

• Consider exposing the readiness probe minPeers and periodSeconds values as chart parameters so users can tune them per environment rather than hardcoding defaults.
• Verify that setting podManagementPolicy to Parallel for the validator StatefulSet does not introduce race conditions or dependency issues during startup, and document any required initialization ordering.
• Double-check that requiring minPeers=1 in readiness checks won't prevent pods from becoming ready in low-peer or single-node setups (e.g., dev/test clusters) where no additional peers are available.

Please address the comments from this code review:

## Overall Comments
- Consider exposing the readiness probe minPeers and periodSeconds values as chart parameters so users can tune them per environment rather than hardcoding defaults.
- Verify that setting podManagementPolicy to Parallel for the validator StatefulSet does not introduce race conditions or dependency issues during startup, and document any required initialization ordering.
- Double-check that requiring minPeers=1 in readiness checks won't prevent pods from becoming ready in low-peer or single-node setups (e.g., dev/test clusters) where no additional peers are available.

Code Review

This pull request introduces parallel deployment for StatefulSets and improves the readiness checks for network nodes. The podManagementPolicy is set to Parallel for validator nodes, which will speed up deployments and scaling. The readiness probe is made more robust by requiring at least one peer (minPeers=1) and more responsive by reducing the check interval to 5 seconds. These changes are well-aligned with best practices for running distributed applications like blockchain nodes on Kubernetes. The documentation and default values have been updated accordingly. The changes are sound and I have not identified any issues.