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

Move "hideous hack" for Kubernetes service network from probe to app #3432

Merged
merged 1 commit into from
Nov 19, 2018

Conversation

bboreham
Copy link
Collaborator

@bboreham bboreham commented Nov 19, 2018

This is to address an inconsistency introduced by #3274, reporting Kubernetes info from a cluster-level probe, and removes a lie from the probe data.

Suggested at #3428 (comment)

Rather than do the work every time the probe sends a report, we do it every time the app renders endpoints, which should be once per merged report set.

Replaces #3428

This avoids side-effects from reporting Kubernetes from a
cluster-level probe, and removes a lie from the probe data.

Rather than do the work every time the probe sends a report, we do it
every time the app renders endpoints, which should be once per merged
report set.
Copy link
Member

@rade rade left a comment

Choose a reason for hiding this comment

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

If the app receives old reports, nothing breaks, it just duplicates some work, right?

LGTM

@bboreham
Copy link
Collaborator Author

If the app receives old reports, nothing breaks, it just duplicates some work, right?

Right, if the probe has already put the service route in then this should re-add it which is a no-op.

@bboreham bboreham merged commit 2e7dff5 into master Nov 19, 2018
@bboreham bboreham deleted the move-hideous-hack branch November 19, 2018 16:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants