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

health_check: Endpoint health_check_config updates not taking effect #4070

Closed
bplotnick opened this issue Aug 6, 2018 · 2 comments
Closed
Assignees
Labels
bug question Questions that are neither investigations, bugs, nor enhancements

Comments

@bplotnick
Copy link
Contributor

Title: health_check: Endpoint health_check_config updates not taking effect

Description:
The health_check_config configuration (i.e. active healthchecking on a different port than the application) does not get applied on endpoint config update.

The specifics of what i've tested are using file-based xDS and then updating the EDS configuration to add a health_check_config. Even though the configuration is updated successfully, the cluster healthchecker does not use this new config.

Repro steps:

I've created a (not-so-minimal) repro for this behavior which is located here: https://github.com/bplotnick/envoy_examples/tree/master/healthcheck_updates

The instructions are in the README there, but it is simply enabling healthchecking and then modifying the EDS file such that it should healthcheck against a different port which, depending on what configuration is being loaded, will either cause healthchecking to begin succeeding or failing

@mattklein123 mattklein123 added the question Questions that are neither investigations, bugs, nor enhancements label Aug 6, 2018
@mattklein123
Copy link
Member

@dio do you mind taking a look? I think this is related to a feature you added. Thank you!

@dio
Copy link
Member

dio commented Aug 7, 2018

Yes sure, been discussing it with @bplotnick on slack.

@dio dio self-assigned this Aug 7, 2018
@dio dio added the bug label Aug 7, 2018
htuch pushed a commit that referenced this issue Aug 17, 2018
This PR makes sure changing health check address triggers rebuilding the cluster.

Risk Level: medium
Testing: unit, manual as depicted by @bplotnick in #4070.
Docs Changes: N/A
Release Notes: N/A

Fixes #4070

Signed-off-by: Dhi Aurrahman <dio@tetrate.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug question Questions that are neither investigations, bugs, nor enhancements
Projects
None yet
Development

No branches or pull requests

3 participants