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.

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

rgw: use insecure TLS for bucket health check (backport #8712) #8855

Merged
merged 1 commit into from Sep 29, 2021

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Sep 28, 2021

This is an automatic backport of pull request #8712 done by Mergify.

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.io/

@mergify mergify bot added the conflicts label Sep 28, 2021
@leseb leseb force-pushed the mergify/bp/release-1.7/pr-8712 branch from 0ff9fd3 to 0540547 Compare September 28, 2021 14:17
Copy link
Member

@leseb leseb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

golang-ci

@leseb leseb force-pushed the mergify/bp/release-1.7/pr-8712 branch from 0540547 to 4e600eb Compare September 28, 2021 15:00
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: #8663
Signed-off-by: Sébastien Han <seb@redhat.com>
(cherry picked from commit cda5dad)
@leseb leseb force-pushed the mergify/bp/release-1.7/pr-8712 branch from 4e600eb to 1ca2f81 Compare September 28, 2021 15:47
Copy link
Member

@leseb leseb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed

@leseb leseb merged commit 89990f7 into release-1.7 Sep 29, 2021
@leseb leseb deleted the mergify/bp/release-1.7/pr-8712 branch September 29, 2021 07:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant