"kubectl attach" command hangs without providing interactive shell following "Share Process Namespace between Containers in a Pod" task about website HOT 9 OPEN

I ran these commands on k8s v1.29 cluster
kubectl attach -it nginx -c shell command does give the following output. I think it needs to be changed in the documentation

The suggested command kubectl exec -it nginx -c shell -- /bin/sh works fine

from website.

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

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

from website.

what works though is
kubectl exec -it nginx -c shell -- /bin/sh

from website.

Page reported in issue (based on issue title): https://kubernetes.io/docs/tasks/configure-pod-container/share-process-namespace/
/language en

from website.

/retitle "kubectl attach" command hangs without providing interactive shell following "Share Process Namespace between Containers in a Pod" task

from website.

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

from website.

I see that this issue is yet to be resolved..If replacing the command in documentation is the right solution then I will raise a PR for the same.

from website.

I tried kubectl attach command with various options. It seems like there is some issue with the command itself at the moment. It gets stuck as shared in screenshots above. Since, kubectl exec command is working fine, I think it can be used without affecting the task in documentation. So I think kubectl attach can be replaced with kubectl exec for now.
@dipesh-rawat what are your views on this? I can raise a PR for the same.

from website.

/remove-lifecycle stale

from website.