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

GCP services don't use configured DNS resolvers #2359

Closed
bruceg opened this issue Apr 17, 2020 · 2 comments
Closed

GCP services don't use configured DNS resolvers #2359

bruceg opened this issue Apr 17, 2020 · 2 comments
Labels
domain: networking Anything related to Vector's networking meta: blocked Anything that is blocked to the point where it cannot be worked on. provider: gcp Anything `gcp` service provider related sink: gcp_cloud_storage Anything `gcp_cloud_storage` sink related sink: gcp_pubsub Anything `gcp_pubsub` sink related sink: gcp_stackdriver_logs Anything `gcp_stackdriver_logs` sink related type: bug A code related bug. type: tech debt A code change that does not add user value.

Comments

@bruceg
Copy link
Member

bruceg commented Apr 17, 2020

In order to use GCP services, clients must first request a token from a separate API. This process happens through a reqwest::Client internal to the goauth library, and so does not use our custom resolver. This needs to be fixed to respect configured DNS servers.
@bruceg bruceg added type: bug A code related bug. domain: networking Anything related to Vector's networking sink: gcp_pubsub Anything `gcp_pubsub` sink related sink: gcp_cloud_storage Anything `gcp_cloud_storage` sink related sink: gcp_stackdriver_logs Anything `gcp_stackdriver_logs` sink related provider: gcp Anything `gcp` service provider related labels Apr 17, 2020
@binarylogic binarylogic added the type: tech debt A code change that does not add user value. label Apr 17, 2020
@lukesteensen lukesteensen mentioned this issue May 18, 2020
Closed
@binarylogic binarylogic added the meta: blocked Anything that is blocked to the point where it cannot be worked on. label Jun 2, 2020
@binarylogic
Copy link
Contributor

This is blocked by the decision in #2635.

@binarylogic
Copy link
Contributor

Closing since we've decided to remove DNS support. Please see https://vector.dev/highlights/2020-06-18-remove-custom-dns-resolution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
domain: networking Anything related to Vector's networking meta: blocked Anything that is blocked to the point where it cannot be worked on. provider: gcp Anything `gcp` service provider related sink: gcp_cloud_storage Anything `gcp_cloud_storage` sink related sink: gcp_pubsub Anything `gcp_pubsub` sink related sink: gcp_stackdriver_logs Anything `gcp_stackdriver_logs` sink related type: bug A code related bug. type: tech debt A code change that does not add user value.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bruceg @binarylogic