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
Describe the bug
Currently automatically generated links point into 443 port (via https prefix). If there's more ingress controllers, they use different ports. So some links are incorrect, because misses valid port
To Reproduce
Steps to reproduce the behavior:
Expose ingress controller on port different than default 443
Links are generated with 443 port
Links doesn't work
Expected behavior
Links should be created with valid port. As we can have multiple ingress controllers supporting the same ingress, we don't know which port to choose, so the easiest way would be to allow to override default 443 port via annotation like:
hajimari.io/port: "2000"
The text was updated successfully, but these errors were encountered:
Describe the bug
Currently automatically generated links point into 443 port (via https prefix). If there's more ingress controllers, they use different ports. So some links are incorrect, because misses valid port
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Links should be created with valid port. As we can have multiple ingress controllers supporting the same ingress, we don't know which port to choose, so the easiest way would be to allow to override default 443 port via annotation like:
hajimari.io/port: "2000"
The text was updated successfully, but these errors were encountered: