Unable to install VMware Data Services Manager Supervisor service on Workload Domain and pod failed to start.

Products

• VMware Data Services Manager for VCF

Issue/Introduction

• When installing the DSM service on the supervisor cluster of a VCF9.0 workload domain, the pod fails to start properly.

• Upon checking POD logs, the below events would show up.

kubectl -n svc-consumption-operator-domain-c10 logs dsm-consumption-operator-controller-manager-65788cdbd-dzmzj
{"level":"error","ts":"2025-09-03T08:09:36.831684765Z","logger":"setup","msg":"unable to create controller","controller":"v1alpha1.PostgresCluster","error":"failed to read the DSM allowed config map: failed to get server groups: Get \"https://172.#.#.1:443/api\": dial tcp 172.2.0.1:443: connect: network is unreachable","stacktrace":"main.setupControllers\n\t/build/mts/release/bora-24665381/dsm-consumption-operator/cmd/main.go:177\nmain.main\n\t/build/mts/release/bora-24665381/dsm-consumption-operator/cmd/main.go:126\nruntime.main\n\t/build/mts/release/bora-24665381/compcache/cayman_go/ob-24502881/linux64/src/runtime/proc.go:272"}

• A VM is placed in the pod's network (172.xx.0.0/28), and can ping the gateway 172.xx.0.1, but may not ping the target 172.yy.0.1 (Destination Net Unreachable).

Environment

VMware Data Services Manager 2.2

Cause

The issue is seen when Distributed Firewall (DFW) on NSX and the Distributed Load balancer (DLB) service are disabled.

Resolution

• Please enable the Distributed Firewall and Distributed Load Balancer service on NSX to resolve the issue.