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 we go through the tutorial, the following VirtualService object will be created.
Is there a way to use a fully qualified domain name (FQDN) in host of the Destination field?
I'm asking this because our k8s has a rule that an FQDN must be specified to the field as Istio recommends.
If it's not possible, as I really need this feature, I may be going to contribute to this project.
I have the following ideas to implement the feature. Let me know which you think is better or if you have a better idea than mine.
Use an FQDN by default
I think it's OK to use an FQDN by default because SeldonDeploument creates a VS and a service in the same namespace, so IIUC using the short name or FQDN doesn't matter.
Add a new option as a helm value such as istio.use_fqdn or as an annotation such as seldon.io/istio-use-fqdn to the SeldonDeployment
The text was updated successfully, but these errors were encountered:
No, seldon.io/istio-host is not what I want IIUC. It's meant to be used for spec.hosts.
I'd like to use a FQDN in the host of Destination field.
ysk24ok
changed the title
How to use an FQDN in a host of Istio VirtualService
How to use an FQDN in a host of Istio VirtualService Destination field
Oct 20, 2022
When we go through the tutorial, the following VirtualService object will be created.
Is there a way to use a fully qualified domain name (FQDN) in
host
of the Destination field?I'm asking this because our k8s has a rule that an FQDN must be specified to the field as Istio recommends.
https://github.com/SeldonIO/seldon-core/blob/v1.14.1/operator/controllers/seldondeployment_controller.go#L353
It doesn't seem possible to me because
pSvcName
is expected to be a service name. It can be customized by passingseldon.io/svc-name
, but it's still just a service name.If it's not possible, as I really need this feature, I may be going to contribute to this project.
I have the following ideas to implement the feature. Let me know which you think is better or if you have a better idea than mine.
istio.use_fqdn
or as an annotation such asseldon.io/istio-use-fqdn
to the SeldonDeploymentThe text was updated successfully, but these errors were encountered: