-
Notifications
You must be signed in to change notification settings - Fork 463
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
Log spam (and higher cpu usage) due to postgres-operator #1458
Labels
Comments
thoro
added a commit
to thoro/kube-router
that referenced
this issue
Mar 30, 2023
… validate if they changed
See #1459 for possible fix |
Seems reasonable. I commented on the PR that you submitted. Thanks for looking into this and submitting a fix! |
thoro
added a commit
to thoro/kube-router
that referenced
this issue
Apr 3, 2023
… validate if they changed
thoro
added a commit
to thoro/kube-router
that referenced
this issue
Apr 3, 2023
… validate if they changed
aauren
pushed a commit
that referenced
this issue
Apr 4, 2023
Fixed via #1461 |
I'll try to do a new RC release either this week or next to incorporate the change. Thanks again for your contribution! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
zalando/postgres-operator users the annotations of the main db service service as a keep alive token. This causes an endpoints update for kube-router.
It will spam the output with lines like:
etc. every second
What did you expect to happen?
Do not consider updates to annotations relevant, since they are not used in building the endpoint information anyways. This means they can be safely ignored
How can we reproduce the behavior you experienced?
Steps to reproduce the behavior:
** System Information (please complete the following information):**
kube-router --version
): [e.g. 1.0.1] 1.5.3The text was updated successfully, but these errors were encountered: