You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the above values in my values.yaml results in only the atlantis.dev.com/ path being resolved by the alb. atlantis.dev.com/events and atlantis.dev.com/status all fail with 404 not found.
see below image of the resulting alb listener rule in aws when using the above values.
Instead i had to add the below values in addition to get it to forward all paths after the slash.
latest
4.0.5
chart.Using the above values in my
values.yaml
results in only theatlantis.dev.com/
path being resolved by the alb.atlantis.dev.com/events
andatlantis.dev.com/status
all fail with 404 not found.see below image of the resulting alb listener rule in aws when using the above values.
Instead i had to add the below values in addition to get it to forward all paths after the slash.
the alb ingressClassName is referring to my deployment of the aws load balancer controller chart version 1.4.1
The text was updated successfully, but these errors were encountered: