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
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
Describe Preferred Solution
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:
startpunkt.ullberg.us/port: "2000"
Describe Alternatives
Can we figure out the port based on the ingress controller (and how does this translate to other ingress types like Routes or Gateway-API?)?
Feature Request
Describe the Feature Request
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
Describe Preferred Solution
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:
Describe Alternatives
Related Code
Additional Context
Based on @Marx2 request for Hajimari (toboshii/hajimari/issues/113)
Also @PrymalInstynct request for Hajimari (toboshii/hajimari/issues/28)
The text was updated successfully, but these errors were encountered: