A BAR file that holds many flows or heavy resources makes the integration server start slowly and use more CPU and memory. When resources are under-allocated, the readiness and liveness checks fail or the container is OOM-killed, so Kubernetes restarts the pod repeatedly. The recommended remedy is to review the pod metrics and raise the limits in the integration server custom resource (spec.pod.containers.runtime.resources.limits and requests for cpu and memory), or to split the flows across more integration servers. Tuning probe values only hides the symptom, clearing trace data has no effect on restarts, and keeping a container alive is a diagnostic technique, not a fix.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit