Comments (6)
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-sigs/prow repository.
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.
In response to this:
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
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-sigs/prow repository.
from ingress-nginx.
Related Issues (20)
- removing ingress Nginx default résponse header HOT 11
- py-lmdb CVE-2019-16224, CVE-2019-16225, CVE-2019-16226, CVE-2019-16227 HOT 8
- Convert multiple path rewrite rules from default.conf to ingress-nginx.yaml HOT 15
- Usage of GeoIP2 variables CRASH the ingress in case maxmind-license is out of download quota (or download fails) HOT 6
- Support per-ingress opentelemetry service naming HOT 3
- GeoIP2 files present in /etc/ingress-controller/geoip, but the controller logs show "GeoLite2-City.mmdb not found" HOT 5
- Route53 DNS problems HOT 6
- tls: failed to verify certificate: x509 HOT 4
- ginkgo bump requirement reported in CI e2e HOT 3
- Add annotation for per-Ingress upstream-keepalive-connections HOT 3
- Vulnerability CVE-2023-44487 in NGINX 1.21.6 reported for controller-v1.9.6 HOT 7
- ingress-nginx chart + terraform = Invalid value: "integer": spec.triggers[1].metadata.value in body must be of type string: "integer" HOT 8
- Possibility to customize the format of error logs and controller logs HOT 2
- GRPCBufferSizeKb Templating Error on 1.10.1 HOT 4
- AWS nginx-ingress-controller context error HOT 6
- Race condition during SNI extraction when TLS ClientHello is fragmented leading to ssl-passthrough being "ignored" HOT 3
- Public IP of Ingress-nginx is not accessible for CAPZ in v1.29.1 HOT 7
- Ingress-NGINX v1.10.1 Feature Availability on Kubernetes v1.30.2 HOT 7
- Update OpenTelemetry Module HOT 3
- A document is needed to explain that the current support for HTTP3 is not complete. HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ingress-nginx.