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
Is your feature request related to a problem? Please describe.
I'm using Label Studio inside a Kubernetes cluster. I need to connect to the S3 storage in the same cluster. However the first problem is that inside the container, label studio needs the internal minio.:9000 to connect to S3 but on the browser when labeling the user needs the external minio..
Neither of these URLS is available in both situations. Fixing this temporarily is adding an entry to the kubernetes local dns so it resolves minio. to minio..
After solving this a new problem occurs. When trying to access a url type task via the presigned urls. I get an error when trying to connect to the URL, there is no TLS inside the kube cluster so I can't just put a certificate in CUSTOM_CA_CERTS and expect it to work for both.
Describe the solution you'd like
It would be nice if I could just skip TLS verification and run in insecure mode.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
TLS security doesn't matter for me because I'm in an air gapped server and all internal communication is insecure. Outside communication is secured by ingress
The text was updated successfully, but these errors were encountered:
Thank you for your feature request regarding optionally bypassing TLS verification! We greatly appreciate your feedback and the opportunity to consider your suggestion. Your request will be evaluated and ranked alongside other roadmap items. If our product team opts to proceed with your idea, we will keep you updated throughout the process. Please understand that while we take all requests seriously, we cannot promise implementation or a specific timeframe.
Is your feature request related to a problem? Please describe.
I'm using Label Studio inside a Kubernetes cluster. I need to connect to the S3 storage in the same cluster. However the first problem is that inside the container, label studio needs the internal minio.:9000 to connect to S3 but on the browser when labeling the user needs the external minio..
Neither of these URLS is available in both situations. Fixing this temporarily is adding an entry to the kubernetes local dns so it resolves minio. to minio..
After solving this a new problem occurs. When trying to access a
url
type task via the presigned urls. I get an error when trying to connect to the URL, there is no TLS inside the kube cluster so I can't just put a certificate inCUSTOM_CA_CERTS
and expect it to work for both.Describe the solution you'd like
It would be nice if I could just skip TLS verification and run in insecure mode.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
TLS security doesn't matter for me because I'm in an air gapped server and all internal communication is insecure. Outside communication is secured by ingress
The text was updated successfully, but these errors were encountered: