Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Websockets support for kic-gateway-api #6331

Open
2 tasks done
rogeriocassares opened this issue Jul 18, 2024 · 2 comments
Open
2 tasks done

Websockets support for kic-gateway-api #6331

rogeriocassares opened this issue Jul 18, 2024 · 2 comments

Comments

@rogeriocassares
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Does this enhancement require public documentation?

  • I have added an Acceptance Criteria item for adding and/or adjusting public documentation (if applicable)

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 (

- Allow the `ws` and `wss` Enterprise protocol values for protocol annotations.
).

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.

@programmer04
Copy link
Member

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

@rogeriocassares
Copy link
Author

rogeriocassares commented Jul 23, 2024

Hi @programmer04 ,

Thanks for your answer!

  1. 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?

  2. 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?

  3. The configuration presented on this topic is allowed outside the Enterprise Edition?
    how to proxy websocket with kong ingress  #995

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?

Many Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants