[bussyjd]

Summary

• Add new Helm value charon.dkgSidecar.targetConfigHash to allow specifying target config hash for DKG cluster selection
• Exposes TARGET_CONFIG_HASH environment variable to the DKG sidecar init container runtime
• Optional parameter that is only set when provided
• Includes comprehensive format validation and test coverage

Changes

1. Core Functionality

• New Parameter: charon.dkgSidecar.targetConfigHash in values.yaml
• Environment Variable: TARGET_CONFIG_HASH conditionally set in StatefulSet
• Format: 32-byte hex hash with 0x prefix (66 characters total)
• Example: 0x7f0fd29abb11674b4e61000de26bff3600237aab0402427bd1409756665c2115

2. Validation (validate.yaml)

Comprehensive format validation catches errors at template-time:

• ✅ Must start with 0x prefix
• ✅ Must be exactly 66 characters (0x + 64 hex digits)
• ✅ Must contain only valid hexadecimal characters (0-9, a-f, A-F)
• ✅ Empty string is allowed (optional parameter)

3. Documentation

• values.yaml: Updated with format requirements and example
• Example file: values-examples/with-target-config-hash.yaml with usage guide
• README: Auto-generated with helm-docs showing validation requirements

4. Test Coverage

Validation Tests (Template-time)

• ✅ Valid hash renders successfully
• ✅ Missing 0x prefix fails with clear error
• ✅ Wrong length fails with clear error
• ✅ Invalid hex characters fails with clear error
• ✅ Empty/unset is allowed

Helm Tests (Runtime)

New test file: test-target-config-hash-set.yaml

• Verifies TARGET_CONFIG_HASH env var is set correctly
• Validates env var matches expected value
• Checks format: 0x prefix, 66 character length
• Clear pass/fail output with diagnostics

Updated test: test-dkg-sidecar-fresh-state.yaml

• Added TARGET_CONFIG_HASH env var to DKG sidecar init container
• Ensures test environment matches production configuration
• Conditional on test values

Usage

Basic Deployment with Target Config Hash

helm install my-dv-pod obol/dv-pod \
  --set charon.dkgSidecar.targetConfigHash=0x7f0fd29abb11674b4e61000de26bff3600237aab0402427bd1409756665c2115 \
  --set charon.operatorAddress=0xYourOperatorAddress \
  --set charon.beaconNodeEndpoints[0]=http://beacon-node:5052 \
  -n dv-namespace --create-namespace

Using Example Values File

helm install my-dv-pod obol/dv-pod \
  -f charts/dv-pod/values-examples/with-target-config-hash.yaml \
  -n dv-namespace --create-namespace

Run Tests

helm test <release-name>

Test Plan

Manual Testing

• Deploy with valid target config hash and verify env var is set
• Deploy without target config hash and verify no env var is set
• Verify DKG sidecar processes the TARGET_CONFIG_HASH correctly
• Test validation rejects invalid formats (missing 0x, wrong length, invalid chars)

Automated Testing

• Template validation tests for all error scenarios
• Helm test pod verifies env var injection
• DKG sidecar integration test includes TARGET_CONFIG_HASH

Breaking Changes

None - this is a new optional parameter with backward-compatible defaults.

Related Issues

Enables DKG sidecar to target specific cluster definitions when multiple invites exist for an operator address.

[OisinKyne]

One tweak