pkg syscall (darwin-arm64), const NOTE_EXIT_DETAIL = 33554432
pkg syscall (darwin-arm64), const NOTE_EXIT_DETAIL ideal-int
pkg syscall (darwin-arm64), const NOTE_EXIT_DETAIL_MASK = 458752
pkg syscall (darwin-arm64), const NOTE_EXIT_DETAIL_MASK ideal-int
pkg syscall (darwin-arm64), const NOTE_EXIT_MEMORY = 131072
pkg syscall (darwin-arm64), const NOTE_EXIT_MEMORY ideal-int

Plexus Archiver junit/textui/TestRunner.class package junit.textui; public synchronized class TestRunner extends junit.runner.BaseTestRunner { private ResultPrinter fPrinter; public static final int SUCCESS_EXIT = 0; public static final int FAILURE_EXIT = 1; public static final int EXCEPTION_EXIT = 2; public void TestRunner(); public void TestRunner(java.io.PrintStream); public void TestRunner(ResultPrinter); public static void run(Class); public static junit.framework.TestResult run(junit.framework.Test);...

pkg syscall (netbsd-arm64-cgo), const NOTE_EXEC = 536870912
pkg syscall (netbsd-arm64-cgo), const NOTE_EXEC ideal-int
pkg syscall (netbsd-arm64-cgo), const NOTE_EXIT = 2147483648
pkg syscall (netbsd-arm64-cgo), const NOTE_EXIT ideal-int
pkg syscall (netbsd-arm64-cgo), const NOTE_EXTEND = 4
pkg syscall (netbsd-arm64-cgo), const NOTE_EXTEND ideal-int
pkg syscall (netbsd-arm64-cgo), const NOTE_FORK = 1073741824

  - Migrate `pkg/kubelet/(dockershim, network)` to structured logging
  Exit code changed from 255 to 1 ([#98939](https://github.com/kubernetes/kubernetes/pull/98939), [@yangjunmyfm192085](https://github.com/yangjunmyfm192085)) [SIG Network and Node]
  - Migrate `pkg/kubelet/certificate` to structured logging

- Added a new `--init-only` command line flag to `kube-proxy`. Setting the flag makes `kube-proxy` perform its initial configuration that requires privileged mode, and then exit. The `--init-only` mode is intended to be executed in a privileged init container, so that the main container may run with a stricter `securityContext`. ([#120864](https://github.com/kubernetes/kubernetes/pull/120864), [@uablrek](https://github.com/uablrek))...

This was designed this way mainly to allow using the same objects "yielded" by dependencies inside of background tasks, because the exit code would be executed after the background tasks were finished.

- Give terminal phase correctly to all pods that will not be restarted. 

  In particular, assign Failed phase to pods which are deleted while pending. Also, assign a terminal 
  phase (Succeeded or Failed, depending on the exit statuses of the pod containers) to pods which
  are deleted while running.
  
  This fixes the issue for jobs using pod failure policy (with JobPodFailurePolicy and PodDisruptionConditions 

  // +optional
  optional k8s.io.apimachinery.pkg.apis.meta.v1.Time startedAt = 1;
}

// ContainerStateTerminated is a terminated state of a container.
message ContainerStateTerminated {
  // Exit status from the last termination of the container
  optional int32 exitCode = 1;

  // Signal from the last termination of the container
  // +optional
  optional int32 signal = 2;

 ([#64792](https://github.com/kubernetes/kubernetes/pull/64792), [@luxas](https://github.com/luxas))

containers can be added to running pods for purposes such as debugging, similar to how `kubectl exec` runs a process in an existing container. Also like `kubectl exec`, no resources are reserved for ephemeral containers and they are not restarted when they exit. Note that container namespace targeting is not yet implemented, so [process namespace sharing](https://kubernetes.io/docs/tasks/configure-pod-container/share-process-namespace/) must be enabled to view process from other containers in the pod. ([...