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 Feb 27, 2023. It is now read-only.
I want to secure communication between dfget client, dragonfly supernode and dfget server with TLS and tried to add a kube-rbac-proxy as a sidecar along with Dragonfly supernode container to achieve this (https://github.com/brancz/kube-rbac-proxy). But I observed that the dfget server endpoint does not currently support TLS, so adding the kube-rbac-proxy will not help.
Is there a reason why dfget server endpoint does not support TLS?
Is there a plan to support this going forward?
Could there be performance impact if this is supported?
Environment
dragonfly version: 1.0.0
dfclient version: 1.0.0
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I want to secure communication between dfget client, dragonfly supernode and dfget server with TLS and tried to add a kube-rbac-proxy as a sidecar along with Dragonfly supernode container to achieve this (https://github.com/brancz/kube-rbac-proxy). But I observed that the dfget server endpoint does not currently support TLS, so adding the kube-rbac-proxy will not help.
Environment
dragonfly version: 1.0.0
dfclient version: 1.0.0
The text was updated successfully, but these errors were encountered: