Newly deployed Antrea Interworking pod in CrashLoopBackOff state

Products

• VMware NSX
• VMware Container Networking with Antrea
• VMware vSphere Kubernetes Service
• VMware vDefend Firewall

Issue/Introduction

• Antrea Interworking is deployed using the following doc.
• Supervisor and VKS clusters are utilizing NSX VPC networks. 
• Post deployment, Interworking pod is in a CrashLoopBackOff state:
  
  kubectl get pods -n vmware-system-antrea
  

  NAME                                READY   STATUS             RESTARTS      AGE
pod/interworking                     2/4     CrashLoopBackOff   6 (24s ago)   3m14s
pod/register                         1/1     Running            0             3m14s

  NAME                           READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/interworking   0/1     1            0           3m14s
deployment.apps/register       1/1     1            1           3m14s

• Running a describe on Interworking pod shows the following error:
  
  kubectl describe pod <interworking-pod> -n vmware-system-antrea
...
Events:
  Type     Reason     Age                   From               Message
  ----     ------     ----                  ----               -------
...
  Warning  Unhealthy  80s                   kubelet            Startup probe failed: I0713 11:50:15.326703     102 main.go:60] connecting to tnproxy
I0713 11:50:15.326734     102 main.go:89] Connecting to tnproxy endpoint unix:///var/run/vmware/nsx-proxy/aphinfoservice.sock
  Warning  BackOff    72s (x2 over 79s)    kubelet  Back-off restarting failed container tn-proxy in pod interworking)
  Warning  Unhealthy  47s                  kubelet  Startup probe failed: I0713 <IP:Port>      31 main.go:60] connecting to tnproxy
I0713 11:50:35.193486      31 main.go:89] Connecting to tnproxy endpoint unix:///var/run/vmware/nsx-proxy/aphinfoservice.sock
2026-07-13T11:50:50.203Z -WARNING NSX 31 [nsx@4413 comp="nsx-cluster-control-plane" s2comp="nsx-rpc" subcomp="golang"] NsxRpcConnection[client: (INACTIVE)] Connect(unix:///var/run/vmware/nsx-proxy/aphinfoservice.sock) failed: err = Failed to connect to /var/run/vmware/nsx-proxy/aphinfoservice.sock; err = dial unix /var/run/vmware/nsx-proxy/aphinfoservice.sock: connect: no such file or directory
I0713 11:50:50.203842      31 main.go:94] failed to connect tnproxy endpoint unix:///var/run/vmware/nsx-proxy/aphinfoservice.sock with error Failed to connect to /var/run/vmware/nsx-proxy/aphinfoservice.sock; err = dial unix /var/run/vmware/nsx-proxy/aphinfoservice.sock: connect: no such file or directory, sleep and retry
E0713 11:50:50.203852      31 main.go:137] failed to probeTnProxy Failed to connect to /var/run/vmware/nsx-proxy/aphinfoservice.sock; err = dial unix /var/run/vmware/nsx-proxy/aphinfoservice.sock: connect: no such file or directory
  Warning  Unhealthy  32s (x8 over 2m22s)  kubelet  Startup probe failed: Get "https://localhost:Port/readyz": dial tcp <IP:Port>: connect: connection refused
  Warning  Unhealthy  32s (x5 over 2m7s)   kubelet  Startup probe failed: command timed out: "/usr/local/bin/tnproxy-prober" timed out after 15s
  Warning  BackOff    31s (x8 over 2m4s)   kubelet  Back-off restarting failed container mp-adapter in pod interworking)

Environment

VMware NSX
VMware vDefend Firewall
VMware vSphere Kubernetes Service
VMware Container Networking with Antrea

Resolution

1. If VKS cluster and NSX Manager are in isolated networks ensure Supervisor Management Proxy is deployed.
2. Antrea Interworking to NSX Manager requires connectivity over ports 1234, 1235 and 443. See required ports.
3. To allow traffic between Antrea and NSX Manager on VPC go to:
   
   NSX > VPCs > Virtual Private Clouds > Additional Configurations > E-W Firewall Rules