-
Notifications
You must be signed in to change notification settings - Fork 477
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
404 when using wildcard gateway with ingress #1264
Comments
Is istio CRD enabled in Higress? https://higress.io/docs/latest/ops/deploy-by-helm/#%E6%94%AF%E6%8C%81-istio-crd%E5%8F%AF%E9%80%89 |
Does the selector of your Gateway resource match the labels of the higress-gateway pods? By default, when installed, the label for higress-gateway is |
Istio CRD enabled in higress. gateway selector is correct - virtualservices binded to that gateway work as expected, but, if gateway works, then ingress doesn't untill i restart higress pods. looks like after pod reloading the ingresses getting higher priority than wildcard gateway and work as expected. |
@nbragin4 Does your higress-gateway pod have this label? Higress standard installation mode does not add this label, did you modify the helm chart to add it yourself? In that case, did you modify anything else? |
If it's convenient, you can enter the higress-controller container and execute the following command to verify the control plane configuration. Please paste the output configuration content. curl localhost:15014/debug/configz |
@johnlanni i redacted sensitive data before submitting issue, it's just redacted sample, original sample consists with
i'll gather debug info when problem shows up again and will send it here. thanks for patience |
If you are reporting any crash or any potential security issue, do not
open an issue in this repo. Please report the issue via ASRC(Alibaba Security Response Center) where the issue will be triaged appropriately.
Ⅰ. Issue Description
Encountering a 404 error when using a wildcard gateway in conjunction with ingress rules. It appears that the wildcard Gateway may be overriding specific non-wildcard ingress rules.
Ⅱ. Describe what happened
When creating a gateway with the following configuration, I intermittently receive a 404 error when accessing specific routes defined by ingress resources.
If there is an exception, please attach the exception trace:
Ⅲ. Describe what you expected to happen
I expected the wildcard gateway to coexist with the non-wildcard ingress rules without causing conflicts, allowing access to both wildcard and specific routes without resulting in 404 errors.
Ⅳ. How to reproduce it (as minimally and precisely as possible)
test.example.com
).Ⅴ. Anything else we need to know?
It would be beneficial to understand if there are any existing mechanisms to resolve priority issues between wildcard gateways and specific ingress rules automatically.
Ⅵ. Environment:
The text was updated successfully, but these errors were encountered: