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

fix vsphere TLS client config overwrite #979

Merged
merged 1 commit into from
May 20, 2021

Conversation

mate4st
Copy link
Contributor

@mate4st mate4st commented May 20, 2021

Which issue(s) this PR fixes
Possible Fix for kubermatic/kubermatic#6859

Special notes for your reviewer:

Optional Release Note:

NONE

@kubermatic-bot kubermatic-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. labels May 20, 2021
@mate4st mate4st requested a review from lsviben May 20, 2021 12:01
@kubermatic-bot kubermatic-bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label May 20, 2021
@lsviben
Copy link
Contributor

lsviben commented May 20, 2021

fix the release note :) . Also the ticket you are referring to is from KKP, you could create a ticket in MC so you can link to it and have it clean.

soapClient.DefaultTransport().TLSClientConfig = &tls.Config{
RootCAs: util.CABundle,
}
soapClient.DefaultTransport().TLSClientConfig.RootCAs = util.CABundle
Copy link
Contributor

Choose a reason for hiding this comment

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

Are we sure soapClient.DefaultTransport().TLSClientConfig is never nil?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It gets initialized in soap.NewClient():

c.t.TLSClientConfig = &tls.Config{InsecureSkipVerify: c.k}

Copy link
Contributor

@xrstf xrstf left a comment

Choose a reason for hiding this comment

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

Q

@kubermatic-bot kubermatic-bot added release-note-none Denotes a PR that doesn't merit a release note. and removed release-note Denotes a PR that will be considered when it comes time to generate release notes. labels May 20, 2021
@kubermatic-bot kubermatic-bot added the lgtm Indicates that a PR is ready to be merged. label May 20, 2021
@kubermatic-bot
Copy link
Contributor

LGTM label has been added.

Git tree hash: eecacd0c0c21664be0bf3ed83ff4a98808379fdc

@lsviben
Copy link
Contributor

lsviben commented May 20, 2021

/approve

1 similar comment
@kron4eg
Copy link
Member

kron4eg commented May 20, 2021

/approve

@kubermatic-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kron4eg, lsviben, WeirdMachine

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubermatic-bot kubermatic-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 20, 2021
@kubermatic-bot kubermatic-bot merged commit b51933b into master May 20, 2021
@kubermatic-bot kubermatic-bot deleted the fix-allow-insecure-overwrite branch May 20, 2021 14:38
@mate4st
Copy link
Contributor Author

mate4st commented Jun 9, 2021

/cherry-pick release/v1.27

@kubermatic-bot
Copy link
Contributor

@WeirdMachine: new pull request created: #996

In response to this:

/cherry-pick release/v1.27

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Denotes that all commits in the pull request have the valid DCO signoff message. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants