-
Notifications
You must be signed in to change notification settings - Fork 23
Open
Description
We have noticed several time that kube-adaptor container restarts with exitCode 1 and reason: error. Below is the event details:
status:
containerStatuses:
- restartCount: 1
started: true
ready: true
name: kube-adaptor
state:
running:
startedAt: '2025-11-15T07:28:40Z'
imageID: 'ixxxxxxxxkube-adaptor@sha256:ed1147362d8853d3266bea19e40a715d9ba779700251956126302af73d4bc138'
image: 'xxxxxxkube-adaptor:2.1.0'
lastState:
terminated:
exitCode: 1
reason: Error
startedAt: '2025-11-15T07:18:51Z'
finishedAt: '2025-11-15T07:28:39Z'
containerID: 'cri-o://e4366602afdd6e3b412c2473e394b1e14b284f85b50e8cd419face288a14755a'
In this case router container is up and running so does this kube-adaptor container restart impact on router container and does that cause any issue in the traffic flow or application communication ?
What remediation steps should I follow to bring this kube-adaptor back to a Ready state and prevent it from entering an Error state again?”
Metadata
Metadata
Assignees
Labels
No labels