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.

Sign up for GitHub

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

Jump to bottom

SCTP nodeport service is not working for all IPs present in the node when ipvs is enabled. #81474

Closed
paulsubrata55 opened this issue Aug 15, 2019 · 3 comments · Fixed by #81477
Closed

SCTP nodeport service is not working for all IPs present in the node when ipvs is enabled. #81474

paulsubrata55 opened this issue Aug 15, 2019 · 3 comments · Fixed by #81477
Labels
area/ipvs area/kube-proxy kind/bug Categorizes issue or PR as related to a bug. sig/network Categorizes an issue or PR as relevant to SIG Network.

Comments

@paulsubrata55
Copy link
Contributor

What happened:
SCTP nodeport service is not working for all IPs present in the node when ipvs is enabled. It is working only for node's InternalIP.

What you expected to happen:
SCTP nodeport service must work for all ips present in the node when ipvs is enabled.

How to reproduce it (as minimally and precisely as possible):
Create a kubernetes cluster with at least one node having multiple interfaces with different IPs. Start an SCTP server deployment. Then create a nodeport service for the same. Now try to reach the service using all the IPs present in that node. The service will be accessible only via node's InternalIP not any other IPs.

Environment:

  • Kubernetes version: v1.15.2
  • OS: ubuntu 18.04
  • Kernel: 4.15.0-54-generic
  • Network plugin and version (if this is a network-related bug): ipset version v6.34
@paulsubrata55 paulsubrata55 added the kind/bug Categorizes issue or PR as related to a bug. label Aug 15, 2019
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Aug 15, 2019
@paulsubrata55
Copy link
Contributor Author

/sig network
/area kube-proxy
/area ipvs

@k8s-ci-robot k8s-ci-robot added sig/network Categorizes an issue or PR as relevant to SIG Network. area/kube-proxy area/ipvs and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Aug 15, 2019
This was referenced Aug 15, 2019
Closed
Merged
@athenabot
Copy link

/triage unresolved

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

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

@k8s-ci-robot k8s-ci-robot added the triage/unresolved Indicates an issue that can not or will not be resolved. label Aug 15, 2019
@andrewsykim
Copy link
Member

/remove-triage unresolved

@k8s-ci-robot k8s-ci-robot removed the triage/unresolved Indicates an issue that can not or will not be resolved. label Aug 15, 2019
@aojea aojea mentioned this issue Sep 30, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/ipvs area/kube-proxy kind/bug Categorizes issue or PR as related to a bug. sig/network Categorizes an issue or PR as relevant to SIG Network.
Projects
None yet
Milestone
No milestone
4 participants
@andrewsykim @k8s-ci-robot @paulsubrata55 @athenabot