Parser does not provide service configurations for TCP sources about distribution HOT 4 CLOSED

Seems siddhi-io-nats source returns null which would have been the reason for the empty deployment info.
Refer https://github.com/siddhi-io/siddhi-io-nats/blob/master/component/src/main/java/io/siddhi/extension/io/nats/source/NATSSource.java#L165

Also, we might have to revisit all the sources which are being bundled in the Siddhi Runner distribution.

from distribution.

As I tested we can access the internal NATS source even without a Kubernetes service. Therefore up to now we do not need that service creation for TCP sources. You can find out more details about external TCP access to the Siddhi sources using Siddhi documentation.

from distribution.

@BuddhiWathsala for port-forwarding, we either need to know about the pod name or the service name. Also, in a production environment, we cannot configure port-forwarding for the external connections. Accessing port-forwarding is only possible for admin privileged.
Hence, let's keep the issue open till we fix sources to expose the deployment configurations.

Let's document handling tcp connections where we request user to avoid auto ingress creation and create ingress or other means to expose the tcp connections. If user decides to use auto ingress creation, steps to configure the nginx to allow tcps.

Does that make sense?

from distribution.

@pcnfernando yes that makes sense. For direct access to the TCP sources, the service creation would be useful. To do that we need to understand a given source getting events that pushed externally or getting events from another service(like NATS or Kafka).

from distribution.