You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
The text was updated successfully, but these errors were encountered:
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>
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
The text was updated successfully, but these errors were encountered: