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
First of all, supporting WebSockets is an Enterprise feature. Could you let me know if you're using an Enterprise Kong Gateway with a valid license? Otherwise, it won't work.
Also please provide a minimal reproducible example of a configuration that doesn't work for you
I am not using the Enterprise License. It is not clear in the Documentation (https://docs.konghq.com/kubernetes-ingress-controller/3.2.x/) the limits of Community Edition. I understood is the same containers, but providing the License key the Enterprise things are allowed, is that right?
Please let me know if the Ingress, not the Gateway API allows to use WebSockets or I will have to provide another Ingress Controller like Istio Ingress, Nginx or which one you better indicates for OpenSource solution?
Since I am a University Researcher and I am deploying an On-Premises with few access just to take the Technology under Proof and establishes a new concept of scalable applications, the Enterprise will have a cost that I could not justfies.
Please can you heklp me answring these questions 1, 2 and 3?
Is there an existing issue for this?
Does this enhancement require public documentation?
Problem Statement
I am using the kic-gateway-api for http routing. Now I need the support for websocket routing using kic-gateway-api in v3.2.
I saw that was something that implements but i could not achieve on my configuration files (
kubernetes-ingress-controller/CHANGELOG.md
Line 540 in 02cb949
Please, anyone can help me?
Proposed Solution
No response
Additional information
No response
Acceptance Criteria
Accept Websocket connection from https://github.com/lorenzodonini/ocpp-go/tree/master/example/1.6/cs repository.
The text was updated successfully, but these errors were encountered: