Scanning port 10247 lead to tcp connection 502 error

[lijiecm]

If you have a safe process to scan local port 10247, Ingress nginx will clean up your backend endpoints. At this time, While you change your http project, Ingress nginx will be reloaded and your tcp connection will have a 502 error.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: lijiecm / name: lijie (f828fc0, f2b4cdb, 0bf9ebd)

[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. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-ci-robot]

Welcome @lijiecm!

It looks like this is your first PR to kubernetes/ingress-nginx 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/ingress-nginx has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @lijiecm. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[strongjz]

Can you clarify what you mean by scanning a port and how it relates to a 502 when backends are not there?

[lijiecm]

Can you clarify what you mean by scanning a port and how it relates to a 502 when backends are not there?

for example ,you have a process used tcp-services, when you update your pod ,ingress controller will be update your tcp backends, but if you requests ingress http://127.0.0.1:10247, lua will use strings "GET / HTTP/1.1" to clean your tcp backends , this time if you have a http service update ,ingress nginx will be reload, all of your tcp service will be 502 error.

[rikatz]

makes sense.

@lijiecm can you sign the CLA please?

Thanks

[lijiecm]

makes sense.

@lijiecm can you sign the CLA please?

Thanks

Done

Thanks

[rikatz]

/ok-to-test

[rikatz]

/lgtm
/approve
Thanks!

[rikatz]

@lijiecm there is a fix on lua code, can you take a look please?

Thanks!!

[lijiecm]

@rikatz done, It looks like the checks passed

[rikatz]

/lgtm
Thanks

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lijiecm, rikatz

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [rikatz]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[strongjz]

/cherry-pick release-1.8

[k8s-infra-cherrypick-robot]

@strongjz: new pull request created: #10222

In response to this:

/cherry-pick release-1.8

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.