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
On podman sites, the default ingress is host, which requires --ingress-host to be provided.
This gives a bad user expirence, as it differs from kubernetes sites where you can simply use skupper init.
The suggestion is to switch the default ingress to none and also set the default --ingress-host (if none provided)
to the fully qualified hostname.
The text was updated successfully, but these errors were encountered:
Hi @fgiorgetti,
Could you help me understand this statement?
From what I know, on podman sites, ingress option can be set to none | external, by default the option is set to ''.
In the first case skupper does not support linking to the current site and so --ingress-host is ignored, while in the other two cases --ingress-host is required. So, if we set ingress to none, why shoud we set the default ingress-host to the FQHN?
Hello @DendoD96 . The goal is actually to set a FQHN when the ingress is set to the default (external), so
that users can simply run a skupper init, without explicitly needing to provide an ingress-host.
Switching the default ingress value to none is not yet settled and it is something to be discussed still.
On podman sites, the default ingress is
host
, which requires--ingress-host
to be provided.This gives a bad user expirence, as it differs from kubernetes sites where you can simply use
skupper init
.The suggestion is to switch the default ingress to
none
and also set the default--ingress-host
(if none provided)to the fully qualified hostname.
The text was updated successfully, but these errors were encountered: