Incorrect kubectl attach commands in image volume documentation

[yanhuan0802]

Description

The image volume documentation contains incorrect kubectl attach commands that will not work as intended.

Problem

The documentation currently uses kubectl attach -it image-volume bash, which:

1. Includes an invalid bash argument (kubectl attach doesn't accept command arguments)
2. Cannot provide interactive shell access when the container's main process is sleep infinity
3. Will result in "Unable to use a TTY" errors for users

Expected Behavior

The documentation should use kubectl exec -it image-volume -- bash to correctly:

• Start a new bash process inside the container
• Provide proper interactive terminal access
• Follow Kubernetes best practices for container interaction

Affected Files

English documentation:

• content/en/docs/tasks/configure-pod-container/image-volumes.md (2 occurrences)
• content/en/blog/_posts/2025-04-29-image-volume-beta/index.md (1 occurrence)

Chinese documentation:

• content/zh-cn/docs/tasks/configure-pod-container/image-volumes.md (2 occurrences)
• content/zh-cn/blog/_posts/2025-04-29-image-volume-beta/index.md (1 occurrence)

Proposed Solution

Replace all instances of:

kubectl attach -it image-volume bash

With:

kubectl exec -it image-volume -- bash

Additional Context

• Related KEP: VolumeSource: OCI Artifact and/or Image enhancements#4639
• Feature blog: https://kubernetes.io/blog/2024/08/16/kubernetes-1-31-image-volume-source
• The issue affects both English and Chinese localizations
• Following contribution guidelines, fixes will be submitted as separate PRs for each language

/sig docs
/language en
/language zh

[k8s-ci-robot]

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.

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-sigs/prow repository.

[yanhuan0802]

/assign