Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

rgw: use insecure TLS for bucket health check #8712

Merged
merged 1 commit into from Sep 28, 2021
Merged

rgw: use insecure TLS for bucket health check #8712

merged 1 commit into from Sep 28, 2021

Commits on Sep 28, 2021

  1. rgw: use insecure TLS for bucket health check 

    We have seen cases where the signed certificate used for the RGW does not
contain the internal DNS endpoint, resulting in the health check to fail
since the certificate is not valid for this domain.
People consuming the gateways by external clients and for specific
domains do not necessarily have the internal DNS configured in the
certificate.
So let's be a bit more flexible and simply ensure a connectivity check
and bypass the certificate validation.

Also, this is fixing the tls code in newS3Agent and adds unit tests.

Closes: rook#8663
Signed-off-by: Sébastien Han <seb@redhat.com>
    @leseb
    leseb committed Sep 28, 2021
    Copy the full SHA
    cda5dad View commit details
    Browse the repository at this point in the history