After adding the service, Windows cannot access the master node server

[lizi3548]

What happened:

When I finish installing the ingress nginx service and successfully start it, my Windows SSH client will disconnect from the master server and ping will not work, but Linux can SSH connect and ping

I deleted the service and it was restored

What you expected to happen:

After installing the service, Windows can SSH connect LAN can access servers

NGINX Ingress controller version (exec into the pod and run nginx-ingress-controller --version.): both 1.8.2 and 1.7.1

Kubernetes version (use kubectl version): v1.28.2

Environment:

• OS (e.g. from /etc/os-release): ubuntu 22.04.3
• Kernel (e.g. uname -a):5.15.0-91-generic
• Install tools: `kubeadm
• Basic cluster related info: root@master:~# kubectl get node -o wide

root@master:~# kubectl get node -o wide NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME master Ready control-plane 3d17h v1.28.2 192.168.1.121 <none> Ubuntu 22.04.3 LTS 5.15.0-91-generic docker://24.0.7 node01 Ready <none> 3d17h v1.28.2 192.168.1.122 <none> Ubuntu 22.04.3 LTS 5.15.0-91-generic docker://24.0.7

• How was the ingress-nginx-controller installed: download https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.8.2/deploy/static/provider/cloud/deploy.yaml kubectl apply -f deploy.yaml

• Current State of the controller: root@master:~# kubectl describe ingressclasses Name: nginx Labels: app.kubernetes.io/component=controller app.kubernetes.io/instance=ingress-nginx app.kubernetes.io/name=ingress-nginx app.kubernetes.io/part-of=ingress-nginx app.kubernetes.io/version=1.8.2 Annotations: <none> Controller: k8s.io/ingress-nginx Events: <none>

• Current state of ingress object, if applicable: `root@master:~# kubectl -n ingress-nginx get all NAME READY STATUS RESTARTS AGE pod/ingress-nginx-admission-create-v5878 0/1 Completed 0 140m pod/ingress-nginx-admission-patch-22nbs 0/1 Completed 1 140m pod/ingress-nginx-controller-88fc77b97-8n5wk 1/1 Running 0 140m

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE service/ingress-nginx-controller LoadBalancer 10.103.145.176 192.168.1.121 80:32102/TCP,443:31419/TCP 140m service/ingress-nginx-controller-admission ClusterIP 10.106.243.108 443/TCP 140m

NAME READY UP-TO-DATE AVAILABLE AGE deployment.apps/ingress-nginx-controller 1/1 1 1 140m

NAME DESIRED CURRENT READY AGE replicaset.apps/ingress-nginx-controller-88fc77b97 1 1 1 140m

NAME COMPLETIONS DURATION AGE job.batch/ingress-nginx-admission-create 1/1 3s 140m job.batch/ingress-nginx-admission-patch 1/1 4s 140m`

### Tasks

[k8s-ci-robot]

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[longwuyuan]

@lizi3548 the information you have posted is not enough to make useful comments.

When you create a new bug report, the template has many questions. Please look at those questions. Then edit the issue description here and answer those questions in it.

/triage needs-information

[k8s-ci-robot]

@longwuyuan: Those labels are not set on the issue: kind//triage, kind/needs-information

In response to [this](https://github.com/kubernetes/ingress-nginx/issues/10890#issuecomment-1903387556): >@lizi3548 the information you have posted is not enough to make useful comments. > >When you create a new bug report, the template has many questions. Please look at those questions. Then edit the issue description here and answer those questions in it. > >/remove-kind >/triage needs-information Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[longwuyuan]

/remove-kind bug

[lizi3548]

/remove-kind bug @longwuyuan I do not understand what you mean,could you please be more detailed

[longwuyuan]

• You are not showing any details of the problem in the ingress-nginx controller.
• Your Windows ssh or windows browser or windows laptop or other such problems should show information like ;
  • commands and outputs
  • log messages
  • configuration details
  • K8S resource states
  • Design details
• That should directly show the problem in the code or in the documented functioning of the ingress-nginx controller.

That is because readers of this issue can not guess the connection between your windows ssh and the ingress-nginx controller.

[github-actions[bot]]

This is stale, but we won't close it automatically, just bare in mind the maintainers may be busy with other tasks and will reach your issue ASAP. If you have any question or request to prioritize this, please reach #ingress-nginx-dev on Kubernetes Slack.