-
Notifications
You must be signed in to change notification settings - Fork 344
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
[Bug]: Ingress jaeger-query should use the default IngressClass if one is not provided #2225
Comments
@Jeansen could you provide the CR used to create your Jaeger instance? If you check how the Jaeger Operator works, it will set the IngressClass only if you provided one to the Jaeger jaeger-operator/pkg/ingress/query.go Line 54 in 76b16a3
If you modify the Ingress created by the Jaeger Operator, it will be reconciled and your changes overwritten. |
|
@iblancasa Well, that's exactly the point. I did not specify an IngressClass and therefore expect the cluster default to be used. |
@Jeansen ok, now I understand. Please, could you modify the title of the issue to |
@iblancasa Of course. And thank you for all the help. Looking forward to that PR. |
…ovided jaegertracing#2225 Signed-off-by: Israel Blancas <[email protected]>
Hi @iblancasa , |
Hi @iblancasa , In the above link the following command is being failed: |
@iblancasa |
I didn't reproduce it. Try installing the latest version.
CNCF Slack channel. |
created a pull request addressing this #2458 |
added function getIngressClass which set default or nginx ingress class to jaeger define ingress for providing loadbalancer IP. Signed-off-by: Gaurav Singh <[email protected]>
* fixes #1568 #2225 added function getIngressClass which set default or nginx ingress class to jaeger define ingress for providing loadbalancer IP. Signed-off-by: Gaurav Singh <[email protected]> * Added test for checking if ingressClass is not set then the default or nginx ingressClass is added to the jaeger ingress. Signed-off-by: Gaurav Singh <[email protected]> * Added request chenges mentioned by iblancasa re: test for checking if ingressClass is not set then the default or nginx ingressClass is added to the jaeger ingress. Signed-off-by: Gaurav Singh <[email protected]> * changed func name from getInClusterAvailableIngressClasses() to getInClusterAvailableIngressClass() and updated manifests Signed-off-by: Gaurav Singh <[email protected]> * fixed formatting Signed-off-by: Gaurav Singh <[email protected]> --------- Signed-off-by: Gaurav Singh <[email protected]> Co-authored-by: Gaurav Singh <[email protected]>
…ctDefaultIngressClass func updated API call to use client.Reader instead of client.Client Signed-off-by: amerlin <[email protected]>
What happened?
When I deploy jaeger the operator also createas an Ingress 'jaeger-query'. Although my kubernes IngressClass is configured as default (there is only one Ingress in my setup) and I also set it to watch for Ingress deployments without an IngressClass, the jaeger Ingress always has an IngressClass of ''.
When I delete the Ingress and recreate it, it has the default IngressClass 'nginx'. But after a while, it is overwritten with '' again. Happens only with jaeger . Other, manually created Ingresses, work just fine!
Steps to reproduce
kubectl get ingress jaeger-query -o yaml > /tmp/ingerss.yaml
kubectl replace -f /tmp/ingress.yaml --force
Expected behavior
Ingress jaeger-query should always have a default IngressClass 'nginx'.
Relevant log output
No response
Screenshot
No response
Additional context
No response
Jaeger backend version
v1.44.0
SDK
No response
Pipeline
No response
Stogage backend
Open-Search
Operating system
Linux, Debian 11
Deployment model
Kubernetes
Deployment configs
No response
The text was updated successfully, but these errors were encountered: