-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Healthchecks duplicated when updating target #7407
Comments
I had the same problem. #7045 |
is there are workaround for this issue? We are facing something similar and it causes several issues with some ratelimited internal services |
@akira28 what version are you running? I believe this should be resolved in a newer version of Kong than
|
@onematchfox I'm trying release 2.6.0, but it seems that it still has the issue. I'll investigate further |
Any news on this one ? I am facing the issue on Kong 2.5.1. When i update the path in the upstream it continues to send healthchecks to the old and new paths |
Dear contributor, |
Summary
Kong version:
2.4.1
Whilst investigating #7406 I noticed that when deleting and adding targets to an upstream, the healthchecks associated with the upstream were duplicated.
Steps To Reproduce
In the logs below, mock endpoint is using httpbin. Healthcheck path is initially set to
/
- which redirects (status301
) - and healthy interval at30
(remains the same throughout). Firstly, the target is firstly deleted and readed to illutstrate the duplicate checks. The healthcheck path is subsequently patched to/status/500
and finally/status/200
to further illustrate the point and perhaps remove any potential suspicion regarding this being the same underlying healthcheck.Additional Details & Logs
$ kong start --vv
)<KONG_PREFIX>/logs/error.log
)https://docs.konghq.com/latest/admin-api/#retrieve-node-information)
The text was updated successfully, but these errors were encountered: