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
When following the instructions to install the portal using ArgoCD, if the configuration is set to use Traefik (i.e. network.ingress_type: traefik) with secure mode enabled (network.traefik.secure: true), the Ingress object fails to create because the generated port names are too long (Kubernetes limits port names to be at most 15 characters, though it seems that it isn't validated in Service objects for whatever reason)
Modifying the Application object provided by the instructions to use a shorter release name makes it go through. See here for where the port name is being used with Ingress and fails to validate.
This could be solved by using trunc in the template to cut off the release name if it's too long, but I'd suggest just sticking with simple port names - port names don't have to be unique other than within the service or pod object itself, and http is just as descriptive as openunison-insecure (within the context of a Service called openunison) to the kind of person that would actually be looking at it.
The text was updated successfully, but these errors were encountered:
When following the instructions to install the portal using ArgoCD, if the configuration is set to use Traefik (i.e.
network.ingress_type: traefik
) with secure mode enabled (network.traefik.secure: true
), the Ingress object fails to create because the generated port names are too long (Kubernetes limits port names to be at most 15 characters, though it seems that it isn't validated in Service objects for whatever reason)Modifying the Application object provided by the instructions to use a shorter release name makes it go through. See here for where the port name is being used with Ingress and fails to validate.
This could be solved by using
trunc
in the template to cut off the release name if it's too long, but I'd suggest just sticking with simple port names - port names don't have to be unique other than within the service or pod object itself, andhttp
is just as descriptive asopenunison-insecure
(within the context of a Service calledopenunison
) to the kind of person that would actually be looking at it.The text was updated successfully, but these errors were encountered: