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
I would like to configure an Ingress Gateway that exposes the service on TCP port 61617 (MQTT+TLS protocol with SSL Passthrough) pointing to both nodes of the Artemis cluster (namely exoo-ss-0 and exoo-ss-1).
Do I have to use Istio ServiceEntry?
I read something about configuring Istio with headless services and Statefulsets and tryed something without success.
Is it possible to have a solution that automatically manages creation/deletion of Artemis nodes depending on the traffic?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi all, as I'm pretty new to Istio I need some help on how to configure it for my use case.
I'm using Artemis broker on kubernetes with this CRD
that creates two statefulsets
and some services
I would like to configure an Ingress Gateway that exposes the service on TCP port 61617 (MQTT+TLS protocol with SSL Passthrough) pointing to both nodes of the Artemis cluster (namely exoo-ss-0 and exoo-ss-1).
Do I have to use Istio ServiceEntry?
I read something about configuring Istio with headless services and Statefulsets and tryed something without success.
Is it possible to have a solution that automatically manages creation/deletion of Artemis nodes depending on the traffic?
Beta Was this translation helpful? Give feedback.
All reactions