Add capability to set timeout for ec2metadata's http client #4280
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.
Currently if we use custom http client, it will take quite a long time for ec2metadata timeout ##2972. We could not able to use workaround for increasing hop as there is infra limit :) for that issue.
This PR will allow us flexibility to have custom http client and custom timeout for ec2metadata at the same time.
Using custom http client is important for us to make high throughput and low latency for our services. https://docs.aws.amazon.com/sdk-for-go/v1/developer-guide/custom-http.html