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
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.
The text was updated successfully, but these errors were encountered:
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.
We have had continuous issues with:
The text was updated successfully, but these errors were encountered: