Difference between revisions of "Kubectl attach"
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
[[Unable to use a TTY]] - container your-container [[did not allocate one]] | [[Unable to use a TTY]] - container your-container [[did not allocate one]] | ||
| + | |||
| + | kubectl attach myalpinedataaccess -i | ||
| + | If you don't see a command prompt, try pressing enter. | ||
| + | Error from server (BadRequest): pod myalpinedataaccess [[does not have a host assigned]] | ||
Revision as of 12:52, 8 February 2024
Unable to use a TTY - container your-container did not allocate one
kubectl attach myalpinedataaccess -i If you don't see a command prompt, try pressing enter. Error from server (BadRequest): pod myalpinedataaccess does not have a host assigned
kubectl attach my-pod -i https://kubernetes.io/docs/reference/kubectl/cheatsheet/#updating-resources
kubectl attach ubuntu -c ubuntu -i -t
spec:
containers:
- name: your-name
image: your-name:latest
tty: true
stdin: true
Related
kubectl exec kubectl debug
See also
- K8s troubleshooting:
kubectl logs, kubectl top, kubectl get events -A, kubectl describe pod, Liveness, Readiness,Kubernetes events, Pulling image, OOMKilled, ProbeWarning, Reason,FailedScheduling,errImagePull, ImagePullBackOff, Kubelet conditions:MemoryPressure, DiskPressure, KubeletHasSufficientPID, KubeletReady, kubectl [ debug | attach | exec ] kubectl cluster-info dump, SimKube, KWOK
Advertising:
