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
{{ message }}
This repository has been archived by the owner on Oct 10, 2023. It is now read-only.
Hi there. It would be very handy if EventStreams could be installed in a "Dev mode" that didn't require all the certificates and the TLS and the whatnot. People kicking tires on the product want to be up and running in minutes, and although I realize security is very important, it can slow people down which causes a drop-off in enthusiasm. A switch on the helm chart to enable or disable TLS would be awesome.
Additionally, when using the beta, I had to connect to the brokers via their internal container addresses. I actually really liked this, as I had my own containers which could connect to Kafka without having to go out through the external proxy. It would be very nice to bring this feature back.
The text was updated successfully, but these errors were encountered:
Re. the 2nd one: no, sorry, we intend to keep all access via the proxy. Firstly, there are cross-cutting concerns and features that need (or will need) to be handled in one place. But also I suspect that ICP itself does some networking cleverness so your Kafka clients won't actually go outside the cluster when accessing the proxy nodeport anyway.
Hi there. It would be very handy if EventStreams could be installed in a "Dev mode" that didn't require all the certificates and the TLS and the whatnot. People kicking tires on the product want to be up and running in minutes, and although I realize security is very important, it can slow people down which causes a drop-off in enthusiasm. A switch on the helm chart to enable or disable TLS would be awesome.
Additionally, when using the beta, I had to connect to the brokers via their internal container addresses. I actually really liked this, as I had my own containers which could connect to Kafka without having to go out through the external proxy. It would be very nice to bring this feature back.
The text was updated successfully, but these errors were encountered: