Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with Kubernetes Service #88101

Open
vishal49naik49 opened this issue Feb 13, 2020 · 2 comments
Open

Issue with Kubernetes Service #88101

vishal49naik49 opened this issue Feb 13, 2020 · 2 comments

Comments

@vishal49naik49
Copy link

@vishal49naik49 vishal49naik49 commented Feb 13, 2020

What happened:
We have a service which opens 30000 port on worker node connecting the pod running on port 3000.
Once the pod on this worker node is deleted, we expect worker node to be non responsive on port 30000. However we see the worker node still provides a response.

What you expected to happen:
If the pod is deleted on the node, worker node should not have responded on port 30000

How to reproduce it (as minimally and precisely as possible):
We can easily reproduce this issue.

Anything else we need to know?:
The service is still running while the pod was deleted on the node

Environment:

  • Kubernetes version (use kubectl version): 1.10

  • Cloud provider or hardware configuration: Azure

  • OS (e.g: cat /etc/os-release): CentOS 7

  • Kernel (e.g. uname -a):
    3.10.0-862.3.2.el7.x86_64 #1 SMP Mon May 21 23:36:36 UTC 2018 x86_64 x86_64 x86_64
    GNU/Linux

  • Install tools:
    Deployed from Chef

  • Network plugin and version (if this is a network-related bug):
    Weave 2.6

  • Others:
    Docker version 19.03.5, build 633a0ea

@vishal49naik49

This comment has been minimized.

Copy link
Author

@vishal49naik49 vishal49naik49 commented Feb 13, 2020

/sig Network

@k8s-ci-robot k8s-ci-robot added sig/network and removed needs-sig labels Feb 13, 2020
@athenabot

This comment has been minimized.

Copy link

@athenabot athenabot commented Feb 13, 2020

/triage unresolved

Comment /remove-triage unresolved when the issue is assessed and confirmed.

🤖 I am a bot run by vllry. 👩‍🔬

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.