grandson ophan process started via kubectl exec not adopted by pid 1

[wingyiu]

What happened?

kubectl exec -- sh

sh-4.2# nohup  sh -c 'sleep 10000' &
sh-4.2# exit

kubectl exec -- sh
sh-4.2# ps -efH
UID         PID   PPID  C STIME TTY          TIME CMD
root        623      0  0 09:51 pts/0    00:00:00 sh -l
root        641    623  0 09:51 pts/0    00:00:00   ps -efH
root        621      0  0 09:50 ?        00:00:00 sleep 1000
root          1      0  0 09:07 ?        00:00:00 /usr/local/bin/dumb-init

sleep process ppid alway 0

What did you expect to happen?

ppid should be 1 (sth like dumb-init)

How can we reproduce it (as minimally and precisely as possible)?

just run the command above

Anything else we need to know?

No response

Kubernetes version

$ kubectl version
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short.  Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"27", GitVersion:"v1.27.2", GitCommit:"7f6f68fdabc4df88cfea2dcf9a19b2b830f1e647", GitTreeState:"clean", BuildDate:"2023-05-17T14:20:07Z", GoVersion:"go1.20.4", Compiler:"gc", Platform:"darwin/amd64"}
Kustomize Version: v5.0.1
Server Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.0", GitCommit:"ab69524f795c42094a6630298ff53f3c3ebab7f4", GitTreeState:"clean", BuildDate:"2021-12-07T18:09:57Z", GoVersion:"go1.17.3", Compiler:"gc", Platform:"linux/amd64"}
WARNING: version difference between client (1.27) and server (1.23) exceeds the supported minor version skew of +/-1

Cloud provider

no

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Install tools

Container runtime (CRI) and version (if applicable)

Related plugins (CNI, CSI, ...) and versions (if applicable)

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[neolit123]

/sig cli