- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for CrashLoopBackOff (0.11 sec)
-
cni/pkg/repair/repair_test_helpers.go
// Container specs var ( brokenInitContainerWaiting = corev1.ContainerStatus{ Name: constants.ValidationContainerName, State: corev1.ContainerState{ Waiting: &corev1.ContainerStateWaiting{ Reason: "CrashLoopBackOff", Message: "Back-off 5m0s restarting failed blah blah blah", }, }, LastTerminationState: corev1.ContainerState{ Terminated: &corev1.ContainerStateTerminated{ ExitCode: constants.ValidationErrorCode,
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Fri May 12 17:39:53 UTC 2023 - 4.7K bytes - Viewed (0) -
cni/pkg/repair/repair_test.go
InitContainerStatus: &corev1.ContainerStatus{ Name: constants.ValidationContainerName, State: corev1.ContainerState{ Waiting: &corev1.ContainerStateWaiting{ Reason: "CrashLoopBackOff", Message: "Back-off 5m0s restarting failed blah blah blah", }, }, LastTerminationState: corev1.ContainerState{ Terminated: &corev1.ContainerStateTerminated{
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Tue Oct 24 03:31:28 UTC 2023 - 10.6K bytes - Viewed (0) -
cni/pkg/repair/repaircontroller.go
key := types.NamespacedName{Name: pod.Name, Namespace: pod.Namespace} // We will get an event every time the pod changes. The repair is not instantaneous, though -- it will only recover // once the pod restarts (in CrashLoopBackoff), which can take some time. // We don't want to constantly try to apply the iptables rules, which is unneeded and will fail. // Instead, we track which UIDs we repaired and skip them if already repaired. //
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Sat Feb 10 00:31:55 UTC 2024 - 10.4K bytes - Viewed (0)