Provide a native encryption of the communication between cloud-edge #266
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
Comments
JoeyHwong-gk
added
the
kind/feature
|
/close |
|
@JoeyHwong-gk: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What would you like to be added/modified:
When using sedna with clients being on different networks, it is safer to encrypt communication to be sure messages are not intercepted. Currently, our data exchange between the server and clients is base on http/ws protocol.
We should add TLS support on the communication between cloud-edge. This option should be configurable through the yaml file. It should allow activation and deactivation, but also allow the user to provide paths of the certificates to be used.
Why is this needed:
In our previous version, there is no particular need to be able to verify client certificates, but it should be definitely added if the cost is low.
The text was updated successfully, but these errors were encountered: