revert from using grpc.NewClient to grpc.Dial #46006
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changelog: fixed a bug where Teleport services could not join the cluster using iam, azure, or tpm methods when the proxy service certificate did not contain IP SANs.
This PR reverts the change from
grpc.Dial
togrpc.NewClient
in #44324ReportSecrets
forwarder to proxy's gRPC insecure server #44324grpc.Dial
is being deprecated in favor ofgrpc.NewClient
, but there's an issue wheregrpc.NewClient
resolves the proxy address to an IP and then fails to verify the proxy cert if it does not contain the IP SAN: grpc/grpc-go#7556