Skip to content
This repository was archived by the owner on Aug 19, 2019. It is now read-only.

Conversation

@igorpeshansky
Copy link
Contributor

No description provided.

Copy link
Contributor

@supriyagarg supriyagarg left a comment

Choose a reason for hiding this comment

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

LGTM

@bmoyles0117
Copy link
Contributor

I would NOT do this. Being that we have the dynamic endpoint discovery in place now.

@igorpeshansky
Copy link
Contributor Author

Yes, we disable Docker polling after failing to reach the socket once, but it still spams the logs. There's an argument for disabling everything else along with it — we can do that. I'd like to keep the instance metadata collection on for now, but I've added the Kubernetes watch.

Copy link
Contributor

@bmoyles0117 bmoyles0117 left a comment

Choose a reason for hiding this comment

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

LGTM

@igorpeshansky igorpeshansky merged commit 4e98f48 into master Mar 31, 2018
@igorpeshansky igorpeshansky deleted the igorp-docker-disable-polling branch March 31, 2018 18:37
igorpeshansky added a commit that referenced this pull request Apr 2, 2018
igorpeshansky added a commit that referenced this pull request Apr 2, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants