fix(helm): use cluster DNS for the node agent

charts/snapshot/templates/daemonset.yaml

@@ -59,6 +59,7 @@ spec:
       hostPID: true
       hostIPC: true
       hostNetwork: true
+      dnsPolicy: ClusterFirstWithHostNet
       {{- with .Values.daemonset.nodeSelector }}
       nodeSelector:
         {{- toYaml . | nindent 8 }}

charts/snapshot/tests/daemonset_dns_test.yaml

@@ -0,0 +1,37 @@
+# SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
+# SPDX-License-Identifier: Apache-2.0
+
+suite: host-networked agent cluster DNS
+templates:
+  - templates/daemonset.yaml
+tests:
+  - it: resolves Kubernetes Services from the host network
+    asserts:
+      - equal:
+          path: spec.template.spec.hostNetwork
+          value: true
+      - equal:
+          path: spec.template.spec.dnsPolicy
+          value: ClusterFirstWithHostNet
+
+  - it: retains cluster DNS for a remote metadata client
+    set:
+      operator.enabled: false
+      provenance.provider:
+        enabled: true
+        kubeconfigSecret: metadata-read-only
+        tlsSecret: webhook-tls
+        caBundle: dGVzdC1jYQ==
+        reflectorUsername: test-reflector
+      daemonset.nodeSelector:
+        kubernetes.io/hostname: node-a
+      daemonset.remoteControlPlane:
+        kubeconfigSecret: metadata-credentials
+        providerNamespace: offloaded
+    asserts:
+      - equal:
+          path: spec.template.spec.hostNetwork
+          value: true
+      - equal:
+          path: spec.template.spec.dnsPolicy
+          value: ClusterFirstWithHostNet

docs/operations/security.md

@@ -13,6 +13,10 @@ Because of this, the agent's namespace must permit privileged pods. On clusters
 that enforce [Pod Security Standards](https://kubernetes.io/docs/concepts/security/pod-security-standards/),
 apply the `privileged` level (or an equivalent exception) to that namespace.
 
+The agent uses `ClusterFirstWithHostNet` DNS policy so its host-networked Pod
+can resolve Kubernetes Services. This also applies to a remote metadata API
+exposed through a Service on a Liqo provider.
+
 ## Seccomp
 
 CRIU requires a seccomp profile to perform checkpoint and restore. The Helm chart