Open shivgana opened 2 weeks ago
The issue may not be directly related to the Bitnami container image/Helm chart, but rather to how the application is being utilized, configured in your specific environment, or tied to a specific scenario that is not easy to reproduce on our side.
If you think that's not the case and are interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.
Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.
Suppose you have any questions about the application, customizing its content, or technology and infrastructure usage. In that case, we highly recommend that you refer to the forums and user guides provided by the project responsible for the application or technology.
With that said, we'll keep this ticket open until the stale bot automatically closes it, in case someone from the community contributes valuable insights.
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.
Name and Version
bitnami/minio:2024.7.4-debian-12-r0
What steps will reproduce the bug?
We have installed minio in a cluster and exposed it to the internet, the same for replication installed in another cluster and exposed. Both minios are exposed with signed certificates. While the site replicating from one cluster minio to another cluster minio failed due to verifying the TLS certificate with an unknown CA. Error:
Didn't find any options to pass the CA for the second minio hosted?
What do you see instead?
shared error in step to reproduce