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

Duplicate listener #7

Closed
rlratcliffe opened this issue Oct 12, 2023 · 1 comment
Closed

Duplicate listener #7

rlratcliffe opened this issue Oct 12, 2023 · 1 comment
Assignees

Comments

@rlratcliffe
Copy link
Collaborator

We have had continuous issues with:

  • camel-web-service pods not being able to restart on their own. Readiness probes error out with EOF, restarting over and over, and needing to be manually restarted. This affects the uptime of pods/natural fast recovery of pods since they get stuck.
  • infinite/every minute duplicate listener errors in both the kuma-cp pod as well as the kuma-sidecar containers of the API pods. This seems to also cause issues with high memory utilization of the kuma-cp pod when there are over 40 pods running. Results in a lot of evicted/errored out kuma-cp pods.
@rlratcliffe rlratcliffe self-assigned this Oct 12, 2023
@rlratcliffe
Copy link
Collaborator Author

The cause has been determined to come from exposing the virtual port a second time on the container/service as part of this commit. This was added in order to allow uptime monitoring to work in Elastic. Removing these duplicate ports breaks uptime monitoring in Elastic (with heartbeat), but considering this issue has a detrimental effect on the uptime of pods, I'm prioritizing fixing this issue at the moment. Will create a bug ticket for Tavros shortly, as changes will need to made there in order to fix uptime monitoring in elastic if users upgrade to this version.

Will add to the release with the mention of the breaking change.

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

No branches or pull requests

1 participant