nut-client - "Connection Refused" despite being able to connect inside dnsutils, and router detects no connection attempt

[Hacksawfred3232]

Exactly as the title says. I can confirm that I can connect to the Network UPS Tools server from inside a container (which uses the IP of the host), the inter-network router sitting between my node and the NUT server can detect this connection. Yet when running the nut-client extension, it reports "Connection refused", yet the router reports no connection. Seems like the extension is broken at the moment, I sincerely doubt Cilium or Multus is causing this issue, as a connection from inside the container is working correctly.

Pod used to test:

apiVersion: v1
kind: Pod
metadata:
  name: dnsutils
  namespace: default
spec:
  containers:
  - name: dnsutils
    image: registry.k8s.io/e2e-test-images/agnhost:2.39
    imagePullPolicy: IfNotPresent
  restartPolicy: Always

[frezbo]

You could test with hostNetwork: true in the pod spec, since extensions runs with hostnetworking

[Hacksawfred3232]

You could test with hostNetwork: true in the pod spec, since extensions runs with hostnetworking

Pod can still connect in hostNetwork, "nut-client" still reporting "connection refused".

[frezbo]

is this with a dns name or an ip, maybe the dns resolution of nut-client is broken

[Hacksawfred3232]

is this with a dns name or an ip, maybe the dns resolution of nut-client is broken

It's with an IP. Also, yes, I dropped dnsutils into kube-system to quickly enable hostNetwork.