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
I have a dragonfly instance deployed in my Kubernetes cluster and I am trying to configure snapshots to an S3 endpoint hosted on a MinIO instance.
The ingress object for the MniIO instance uses a certificate signed by an internal CA, not publicly trusted. This causes the dragonfly snapshot to fail on the SSL verification step and not taking any snapshots.
To Reproduce
Steps to reproduce the behavior:
Deploy a MinIO instance with a TLS cert signed by a custom CA
Deploy a Dragonfly instance that attempts to push snapshots to that MinIO instance
See error on TLS verification
Expected behavior
I would expect to be able to somehow either:
disable SSL verification so I can bypass this error,
configure a custom certificate for the SSL verification so I can make my minio cert trusted
Environment (please complete the following information):
Containerized?: yes. Issue spotted in Kubernetes, troubleshooting was done via Docker
Dragonfly Version: 1.25.5
Additional context
I think this is a fairly common setup for corporate environments, having an internal CA that is not publicly trusted.
The text was updated successfully, but these errors were encountered:
Describe the bug
I have a dragonfly instance deployed in my Kubernetes cluster and I am trying to configure snapshots to an S3 endpoint hosted on a MinIO instance.
The ingress object for the MniIO instance uses a certificate signed by an internal CA, not publicly trusted. This causes the dragonfly snapshot to fail on the SSL verification step and not taking any snapshots.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I would expect to be able to somehow either:
Environment (please complete the following information):
Additional context
I think this is a fairly common setup for corporate environments, having an internal CA that is not publicly trusted.
The text was updated successfully, but these errors were encountered: