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

ipvs NodePort is not working if host not using eth{i} as nic name in 1.9.0 #58202

Closed
gyliu513 opened this Issue Jan 12, 2018 · 7 comments

Comments

Projects
None yet
4 participants
@gyliu513
Member

gyliu513 commented Jan 12, 2018

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

/kind feature

What happened:
Deploy an application as following:

apiVersion: v1
kind: Service
metadata:
  labels:
    run: my-nginx
  name: my-nginx
  namespace: default
spec:
  ports:
  - name: nginx
    port: 80
    protocol: TCP
    targetPort: 80
  selector:
    run: my-nginx
  type: NodePort
---
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  labels:
    run: my-nginx
  name: my-nginx
  namespace: default
spec:
  replicas: 1
  selector:
    matchLabels:
      run: my-nginx
  template:
    metadata:
      labels:
        run: my-nginx
    spec:
      containers:
      - image: nginx:1.8.1
        imagePullPolicy: IfNotPresent
        name: my-nginx
        ports:
        - containerPort: 80
          protocol: TCP

After application deployed:

[root@ib17b08 cases]# kubectl get svc
NAME         TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)        AGE
kubernetes   ClusterIP   10.0.0.1     <none>        443/TCP        1h
my-nginx     NodePort    10.0.0.13    <none>        80:30731/TCP   19m

ClusterIP works fine

[root@ib17b08 cases]# curl 10.0.0.13
<!DOCTYPE html>
<html>
<head>
<title>Welcome to nginx!</title>
<style>
    body {
        width: 35em;
        margin: 0 auto;
        font-family: Tahoma, Verdana, Arial, sans-serif;
    }
</style>
</head>
<body>
<h1>Welcome to nginx!</h1>
<p>If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.</p>

<p>For online documentation and support please refer to
<a href="http://nginx.org/">nginx.org</a>.<br/>
Commercial support is available at
<a href="http://nginx.com/">nginx.com</a>.</p>

<p><em>Thank you for using nginx.</em></p>
</body>
</html>

NodePort does not work

[root@ib17b08 cases]# curl 9.21.53.18:30731
^C

/cc @m1093782566
/sig network
/area ipvs
What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

  • Kubernetes version (use kubectl version):
  • Cloud provider or hardware configuration:
  • OS (e.g. from /etc/os-release):
  • Kernel (e.g. uname -a):
  • Install tools:
  • Others:
@gyliu513

This comment has been minimized.

Show comment
Hide comment
@gyliu513

gyliu513 Jan 12, 2018

Member

I think we should merge #55923 back to 1.9.0

Member

gyliu513 commented Jan 12, 2018

I think we should merge #55923 back to 1.9.0

@gyliu513 gyliu513 changed the title from ipvs NodePort is not working if host not using eth{i} as nic name in 1.9 to ipvs NodePort is not working if host not using eth{i} as nic name in 1.9.0 Jan 12, 2018

@Lion-Wei

This comment has been minimized.

Show comment
Hide comment
@Lion-Wei

Lion-Wei Jan 13, 2018

Contributor

Yeah, this pr #56685 do solved this problem, maybe we should cherry-pick this to 1.9.0.
@m1093782566

Contributor

Lion-Wei commented Jan 13, 2018

Yeah, this pr #56685 do solved this problem, maybe we should cherry-pick this to 1.9.0.
@m1093782566

@gyliu513

This comment has been minimized.

Show comment
Hide comment
@gyliu513

gyliu513 Jan 13, 2018

Member

Thanks @Lion-Wei , I think that it should be in 1.9.0, otherwise, we cannot claim that ipvs is beta. @m1093782566

Member

gyliu513 commented Jan 13, 2018

Thanks @Lion-Wei , I think that it should be in 1.9.0, otherwise, we cannot claim that ipvs is beta. @m1093782566

@gyliu513

This comment has been minimized.

Show comment
Hide comment
@gyliu513

gyliu513 Jan 22, 2018

Member

It is a serious bug for ipvs, if we cannot back merge this to 1.9.x, we may not able to claim that ipvs is beta in 1.9.x @Lion-Wei @m1093782566

Member

gyliu513 commented Jan 22, 2018

It is a serious bug for ipvs, if we cannot back merge this to 1.9.x, we may not able to claim that ipvs is beta in 1.9.x @Lion-Wei @m1093782566

@Lion-Wei

This comment has been minimized.

Show comment
Hide comment
@Lion-Wei

Lion-Wei Jan 22, 2018

Contributor

Sorry for didn't handled promptly. : (

Contributor

Lion-Wei commented Jan 22, 2018

Sorry for didn't handled promptly. : (

@fejta-bot

This comment has been minimized.

Show comment
Hide comment
@fejta-bot

fejta-bot Apr 22, 2018

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot commented Apr 22, 2018

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@fejta-bot

This comment has been minimized.

Show comment
Hide comment
@fejta-bot

fejta-bot May 22, 2018

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

fejta-bot commented May 22, 2018

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment