-
Notifications
You must be signed in to change notification settings - Fork 35
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
Selenium URL issue with Custom Ingress (Moon2) #125
Comments
You have to map /wd/hub path to moon service in your ingress configuration,
Take a look how it is implemented in default ingress configuration.
вт, 22 мар. 2022 г., 18:24 achandwaniya-srcit ***@***.***>:
… With Custom Ingress, while accessing Selenium URL ex: "
moon.aerokube.local/wd/hub" it gives 404 error.
But while using the default configuration with default Ingress its working
fine.
Please refer the below screenshot:
With CustomIngress (IngressClass: alb):
[image: image]
<https://user-images.githubusercontent.com/97426832/159516188-37dded76-3d02-45fb-a60a-e51b59d49025.png>
With default Ingress (nginx):
[image: image]
<https://user-images.githubusercontent.com/97426832/159516489-7935fcb7-12f3-4951-8079-24285c6cab7b.png>
—
Reply to this email directly, view it on GitHub
<#125>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKY23KIYJ7NXROVVA4HIB3VBHQ3PANCNFSM5RLH7UTA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Hi aandryashin, But I tried that, by mapping /wd/hub path to moon service as defined in the default ingress configuration. But it still throws 404 error. Host: https://moon.domain.com/ - working - UI accessable I have explored further and found that path: / in ingress object should be treated as /* in alb ingress controller implementation. So for that I passed path as a wildcard but still it didn't worked.
Here is my custom Ingress configuration: I have also tried the default helm chart with default ingress and all the paths are working fine with that, the only issue is with the alb ingressClass. Earlier I have deployed moon v1 on the same cluster with alb ingressClass, and that's working fine. but with moon2 its not working. Also, I have also tried to expose moon service using port-forward but it also didn't work locally. Actually with moon2 earlier the setting of customIngress was missing. So I requested to add that. But it might possible with customIngress moon service chart some configuration missing...is it? or am I doing something wrong? |
You have to map exact /wd/hub and not /wd/hub/ and not /wd/hub/*
There is difference. Moon handles version on exact /wb/hub path, other
subpaths handled by other logic.
чт, 24 мар. 2022 г., 18:33 achandwaniya-srcit ***@***.***>:
… Hi aandryashin,
Thank you for the suggestion!!
But I tried that, by mapping /wd/hub path to moon service as defined in
the default ingress configuration. But it still throws 404 error.
I have explored further and found that path: / in ingress object should be
treated as /* in alb ingress controller implementation. So for that I
passed path as a wildcard but still it didn't worked.
- tried both the ways:
paths:
- path: /wd/hub/*
port: 4444
paths:
- path: /wd/hub/
port: 4444
Here is my custom Ingress configuration:
[image: image]
<https://user-images.githubusercontent.com/97426832/159931801-845e6d4b-e672-4e0f-899f-938401241a15.png>
[image: image]
<https://user-images.githubusercontent.com/97426832/159910811-eefe638e-73a7-4296-b3b5-e260924c8570.png>
I have also tried the default helm chart with default ingress and all the
paths are working fine with that, the only issue is with the alb
ingressClass.
Earlier I have deployed moon v1 on the same cluster with alb ingressClass,
and that's working fine. but with moon2 its not working.
Actually with moon2 earlier the setting of customIngress was missing. So I
requested to add that. But it might possible with customIngress moon
service chart some configuration missing...is it? or am I doing something
wrong?
—
Reply to this email directly, view it on GitHub
<#125 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKY23IJSDFDIDVWHELQU3TVBSDL7ANCNFSM5RLH7UTA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I have tried the exact path /wd/hub as well, as mentioned in the above comment. |
@achandwaniya-srcit did you manage to find any solution? |
Hi @vania-pooh, |
Have the same problem #83 |
With Custom Ingress, while accessing Selenium URL ex: "moon.aerokube.local/wd/hub" it gives 404 error.
But while using the default configuration with default Ingress its working fine.
Please refer the below screenshot:
With default Ingress (nginx):
With custom Ingress (alb)
The text was updated successfully, but these errors were encountered: