checkOverlap is a little loose. about ingress-nginx HOT 6 CLOSED

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.

from ingress-nginx.

/kind bug

from ingress-nginx.

There is a solution, which is to place the newly added rule at the position of rule [0] and move the original rule [0] to rule [1], similar to the head insertion method.
Adding one rule, admission can detect conflicts, but when adding multiple rules, if the first one is new, then there is still a problem.

from ingress-nginx.

/remove-kind bug
/kind support

Hi,

Pasting couple of yaml files and writing couple of short sentences is not enough for the readers to analyze and triage a problem or a bug. It causes readers to guess a lot and assume multiple factors.

If you can look at the template of a new bug report and edit your issue description to answer those questions, it may provide readers with more data to analyze.

Actually please run the tests in a minikube or a kind cluster. And copy/paste the data that is related to the problem so that readers do not have to guess the config and environment. If your tests and the data you post from your tests shows the real state of the cluster and the resources in the cluster (using kubectl and curl commands), it will reduce the time for a developer to reproduce the problem and look for a solution.

/triage needs-information

from ingress-nginx.

The problem description you provided does not contain the information that is asked in a new bug report template. Your issue description also does not provide any outputs of kubectl commands or curl commands, showing a real live cluster and the resources in the cluster or the response to HTTP requests or the logs of the controller pod for those requests.

So a reader must guess and assume a lot of aspects and that is not helpful as the time and resources are short. Also not many people are reporting the same issue.

So please create a cluster in kind or minikube and do the testing of what you want to report. Make sure to copy/paste all the information from your tests here that shows the bug or the problem. Please include the output of kubectl describe commands and logs and curl command outputs with -v.. This will help a reader to confirm the problem and then it will also help others to reproduce the problem. It will also help verify the solution you will test in your cluster.

Once you have posted that information here in the issue description, please feel free to re-open this issue. There are too many open isuses with no real information to take action on and it becomes harder to track actionable bug reports. So I will close this issue now for you to re-open after you have posted the information requested.

/close

from ingress-nginx.

@longwuyuan: Closing this issue.

from ingress-nginx.