Kubernetes基本命令总结
首先
以下是k8s基本命令的总结。为了避免重复查找，我已经整理好了。请随意使用！
当想要查看Pod和复制套件的基本信息（数量确认，正在运行的项目等）时。
kubectl get pods
kubectl get rs
※ レスポンス例
NAME DESIRED CURRENT READY AGE
new-replica-set 4 4 0 56s
当想要查看Replica Set的详细信息时（例如，确认使用的镜像，了解Pod停止工作的原因等）。
kubectl describe pods
※ レスポンス例（ポッド）
ace: default
Priority: 0
Service Account: default
Node: controlplane/172.25.0.33
Start Time: Tue, 28 Mar 2023 11:11:44 +0000
Labels: name=busybox-pod
Annotations: <none>
Status: Pending
IP: 10.42.0.9
IPs:
IP: 10.42.0.9
Controlled By: ReplicaSet/new-replica-set
Containers:
busybox-container:
Container ID:
Image: busybox777
Image ID:
Port: <none>
Host Port: <none>
Command:
sh
-c
echo Hello Kubernetes! && sleep 3600
State: Waiting
Reason: ImagePullBackOff
Ready: False
Restart Count: 0
Environment: <none>
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-w6crj (ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
kube-api-access-w6crj:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional: <nil>
DownwardAPI: true
QoS Class: BestEffort
Node-Selectors: <none>
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 15m default-scheduler Successfully assigned default/new-replica-set-bv9br to controlplane
Normal Pulling 14m (x4 over 15m) kubelet Pulling image "busybox777"
Warning Failed 14m (x4 over 15m) kubelet Failed to pull image "busybox777": rpc error: code = Unknown desc = failed to pull and unpack image "docker.io/library/busybox777:latest": failed to resolve reference "docker.io/library/busybox777:latest": pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
Warning Failed 14m (x4 over 15m) kubelet Error: ErrImagePull
Warning Failed 14m (x6 over 15m) kubelet Error: ImagePullBackOff
Normal BackOff 43s (x64 over 15m) kubelet Back-off pulling image "busybox777"
Name: new-replica-set-hz4d2
Namespace: default
Priority: 0
Service Account: default
Node: controlplane/172.25.0.33
Start Time: Tue, 28 Mar 2023 11:11:44 +0000
Labels: name=busybox-pod
Annotations: <none>
Status: Pending
IP: 10.42.0.11
IPs:
IP: 10.42.0.11
Controlled By: ReplicaSet/new-replica-set
Containers:
busybox-container:
Container ID:
Image: busybox777
Image ID:
Port: <none>
Host Port: <none>
Command:
sh
-c
echo Hello Kubernetes! && sleep 3600
State: Waiting
Reason: ImagePullBackOff
Ready: False
Restart Count: 0
Environment: <none>
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-ntpmm (ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
kube-api-access-ntpmm:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional: <nil>
DownwardAPI: true
QoS Class: BestEffort
Node-Selectors: <none>
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 15m default-scheduler Successfully assigned default/new-replica-set-hz4d2 to controlplane
Normal Pulling 14m (x4 over 15m) kubelet Pulling image "busybox777"
Warning Failed 14m (x4 over 15m) kubelet Failed to pull image "busybox777": rpc error: code = Unknown desc = failed to pull and unpack image "docker.io/library/busybox777:latest": failed to resolve reference "docker.io/library/busybox777:latest": pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
Warning Failed 14m (x4 over 15m) kubelet Error: ErrImagePull
Warning Failed 14m (x6 over 15m) kubelet Error: ImagePullBackOff
Normal BackOff 43s (x65 over 15m) kubelet Back-off pulling image "busybox777"
Name: new-replica-set-h9ms4
Namespace: default
Priority: 0
Service Account: default
Node: controlplane/172.25.0.33
Start Time: Tue, 28 Mar 2023 11:11:44 +0000
Labels: name=busybox-pod
Annotations: <none>
Status: Pending
IP: 10.42.0.12
IPs:
IP: 10.42.0.12
Controlled By: ReplicaSet/new-replica-set
Containers:
busybox-container:
Container ID:
Image: busybox777
Image ID:
Port: <none>
Host Port: <none>
Command:
sh
-c
echo Hello Kubernetes! && sleep 3600
State: Waiting
Reason: ImagePullBackOff
Ready: False
Restart Count: 0
Environment: <none>
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-rw67h (ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
kube-api-access-rw67h:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional: <nil>
DownwardAPI: true
QoS Class: BestEffort
Node-Selectors: <none>
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 15m default-scheduler Successfully assigned default/new-replica-set-h9ms4 to controlplane
Normal Pulling 14m (x4 over 15m) kubelet Pulling image "busybox777"
Warning Failed 14m (x4 over 15m) kubelet Failed to pull image "busybox777": rpc error: code = Unknown desc = failed to pull and unpack image "docker.io/library/busybox777:latest": failed to resolve reference "docker.io/library/busybox777:latest": pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
Warning Failed 14m (x4 over 15m) kubelet Error: ErrImagePull
Warning Failed 13m (x6 over 15m) kubelet Error: ImagePullBackOff
Normal BackOff 40s (x64 over 15m) kubelet Back-off pulling image "busybox777"
Name: new-replica-set-4w8ln
Namespace: default
Priority: 0
Service Account: default
Node: controlplane/172.25.0.33
Start Time: Tue, 28 Mar 2023 11:11:44 +0000
Labels: name=busybox-pod
Annotations: <none>
Status: Pending
IP: 10.42.0.10
IPs:
IP: 10.42.0.10
Controlled By: ReplicaSet/new-replica-set
Containers:
busybox-container:
Container ID:
Image: busybox777
Image ID:
Port: <none>
Host Port: <none>
Command:
sh
-c
echo Hello Kubernetes! && sleep 3600
State: Waiting
Reason: ImagePullBackOff
Ready: False
Restart Count: 0
Environment: <none>
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-kl5tb (ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
kube-api-access-kl5tb:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional: <nil>
DownwardAPI: true
QoS Class: BestEffort
Node-Selectors: <none>
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 15m default-scheduler Successfully assigned default/new-replica-set-4w8ln to controlplane
Normal Pulling 14m (x4 over 15m) kubelet Pulling image "busybox777"
Warning Failed 14m (x4 over 15m) kubelet Failed to pull image "busybox777": rpc error: code = Unknown desc = failed to pull and unpack image "docker.io/library/busybox777:latest": failed to resolve reference "docker.io/library/busybox777:latest": pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
Warning Failed 14m (x4 over 15m) kubelet Error: ErrImagePull
Warning Failed 13m (x6 over 15m) kubelet Error: ImagePullBackOff
Normal BackOff 43s (x64 over 15m) kubelet Back-off pulling image "busybox777"
kubectl describe rs
※ レスポンス例（レプリカセット）
Name: new-replica-set
Namespace: default
Selector: name=busybox-pod
Labels: <none>
Annotations: <none>
Replicas: 4 current / 4 desired
Pods Status: 0 Running / 4 Waiting / 0 Succeeded / 0 Failed
Pod Template:
Labels: name=busybox-pod
Containers:
busybox-container:
Image: busybox777
Port: <none>
Host Port: <none>
Command:
sh
-c
echo Hello Kubernetes! && sleep 3600
Environment: <none>
Mounts: <none>
Volumes: <none>
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal SuccessfulCreate 6m43s replicaset-controller Created pod: new-replica-set-bv9br
Normal SuccessfulCreate 6m43s replicaset-controller Created pod: new-replica-set-4w8ln
Normal SuccessfulCreate 6m43s replicaset-controller Created pod: new-replica-set-hz4d2
Normal SuccessfulCreate 6m43s replicaset-controller Created pod: new-replica-set-h9ms4
想要删除Pod时
kubectl delete pod <pod-name>
请大家考虑以下内容。
这个Udemy的课程详细解释了Kubernetes。
即使是初学者也能轻松理解，并提供了执行环境，无需进行繁琐的环境配置。
如果你对此感兴趣的话，不妨来参加一下吧！
