fix(zookeeper): add publishNotReadyAddresses to headless service

The headless service governing the ZK StatefulSet was missing
publishNotReadyAddresses: true. With K8s 1.22+ EndpointSlice handling
(strict in 1.33+ where the legacy Endpoints API is deprecated),
CoreDNS withholds DNS records for pods whose readiness probe has not
yet passed.

For a StatefulSet that needs sibling DNS to bootstrap a quorum (as ZK
does), this creates a chicken-and-egg deadlock:
  zk-0 starts -> looks up DNS for zk-1, zk-2 -> NXDOMAIN
       -> can't form quorum -> not Ready -> own DNS not published
       -> same for zk-1 and zk-2 -> cluster never forms.

Symptoms in CI logs:
  WARN [WorkerSender] Failed to resolve address:
  zookeeper-1.zookeeper.<ns>.svc.cluster.local
  java.net.UnknownHostException

Reproduced locally on a kind v0.30.0 / k8s 1.34 cluster; verified
patching the live service with publishNotReadyAddresses fixed it.

This bug went unnoticed for years because pre-K8s-1.22 CoreDNS was
lenient about the legacy Endpoints API's notReadyAddresses path.
The lint-test-fid CI started failing in April 2026 when
helm/kind-action@v1 (a floating tag) rolled forward to a release
using kindest/node:v1.35.0, which strictly enforces the readiness
condition on EndpointSlice entries.

Bumps zookeeper chart version 0.1.6 -> 0.1.7. No app changes.

Author: gnanirahulnutakki

charts/zookeeper/Chart.yaml

@@ -15,7 +15,7 @@ type: application
 # This is the chart version. This version number should be incremented each time you make changes
 # to the chart and its templates, including the app version.
 # Versions are expected to follow Semantic Versioning (https://semver.org/)
-version: 0.1.6
+version: 0.1.7
 
 # This is the version number of the application being deployed. This version number should be
 # incremented each time you make changes to the application. Versions are not expected to

charts/zookeeper/templates/service.yaml

@@ -8,6 +8,11 @@ spec:
   type: {{ .Values.service.type }}
 {{- if contains "ClusterIP" .Values.service.type }}
   clusterIP: None
+  # Required for StatefulSet pod-DNS resolution during cluster bootstrap.
+  # ZK pods need DNS for sibling pods (zookeeper-0,1,2) BEFORE they are Ready
+  # so they can form a quorum. Without this, K8s 1.22+ EndpointSlice handling
+  # withholds DNS records until pods are Ready -> chicken-and-egg deadlock.
+  publishNotReadyAddresses: true
 {{- end }}
   ports:
     - port: {{ .Values.service.port }}