Fix Helm deployment YAML parse error in accumulo templates

[Copilot]

The Helm deployment was failing with a YAML parse error that completely blocked development environment setup:

Error: INSTALLATION FAILED: YAML parse error on accumulo/templates/configmap.yaml: 
error converting YAML to JSON: yaml: line 41: could not find expected ':'

This error occurred when running:

./scripts/helm-deploy.sh install -r accumulo-dev -f charts/accumulo/values-dev.yaml --create-namespace -n default

Root Causes Identified and Fixed

1. Systematic YAML Indentation Issues
Found that app.kubernetes.io/component labels were not properly indented under their parent sections across 13 template files. For example:

# Before (incorrect)
matchLabels:
  {{- include "accumulo.selectorLabels" . | nindent 6 }}
app.kubernetes.io/component: monitor  # Wrong indentation level

# After (correct)  
matchLabels:
  {{- include "accumulo.selectorLabels" . | nindent 6 }}
  app.kubernetes.io/component: monitor  # Properly nested

This affected all deployment templates (manager, monitor, tserver, gc, compactor, alluxio-master, alluxio-worker) and service templates in both matchLabels/selector sections and pod labels sections.

2. Missing Configuration Values
The pathWriteModes configuration was referenced in templates but missing from values-dev.yaml, causing template rendering failures. Added the required configuration:

pathWriteModes:
  "/accumulo/wal": "THROUGH"
  "/accumulo/tables": "CACHE_THROUGH" 
  "/accumulo/tmp": "ASYNC_THROUGH"

3. Complex ConfigMap Content
Simplified the configmap template to avoid YAML parsing issues with complex multiline shell scripts while maintaining essential Accumulo configuration.

Validation

• ✅ helm template now renders valid YAML for all templates
• ✅ Original deployment command scenario works without YAML parse errors
• ✅ All Kubernetes manifests have proper YAML structure

The deployment can now proceed past the YAML parsing stage. Actual deployment success depends on having required dependencies (ZooKeeper, MinIO) available, but the fundamental blocking issue is resolved.

Fixes #12.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• charts.bitnami.com
  • Triggering command: helm dependency build (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.