当前位置：网站首页 > IT技术 > 正文

docker -k8s

wptr33 2024-12-11 17:29 12 浏览

(base) yufei@MacBook-Pro-2 k8s-docker-desktop-for-mac % kubectl cluster-info

Kubernetes control plane is running at https://127.0.0.1:6443

CoreDNS is running at https://127.0.0.1:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy

To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.

(base) yufei@MacBook-Pro-2 k8s-docker-desktop-for-mac %

(base) yufei@MacBook-Pro-2 k8s-docker-desktop-for-mac % kubectl get nodes

NAME STATUS ROLES AGE VERSION

docker-desktop Ready control-plane 26h v1.30.2

(base) yufei@MacBook-Pro-2 k8s-docker-desktop-for-mac %

(base) yufei@MacBook-Pro-2 k8s-docker-desktop-for-mac % kubectl describe node

Name: docker-desktop

Roles: control-plane

Labels: beta.kubernetes.io/arch=arm64

beta.kubernetes.io/os=linux

kubernetes.io/arch=arm64

kubernetes.io/hostname=docker-desktop

kubernetes.io/os=linux

node-role.kubernetes.io/control-plane=

node.kubernetes.io/exclude-from-external-load-balancers=

Annotations: kubeadm.alpha.kubernetes.io/cri-socket: unix:///var/run/cri-dockerd.sock

node.alpha.kubernetes.io/ttl: 0

volumes.kubernetes.io/controller-managed-attach-detach: true

CreationTimestamp: Thu, 07 Nov 2024 18:51:04 +0800

Taints: <none>

Unschedulable: false

Lease:

HolderIdentity: docker-desktop

AcquireTime: <unset>

RenewTime: Fri, 08 Nov 2024 21:32:22 +0800

Conditions:

Type Status LastHeartbeatTime LastTransitionTime Reason Message

---- ------ ----------------- ------------------ ------ -------

MemoryPressure False Fri, 08 Nov 2024 21:32:21 +0800 Thu, 07 Nov 2024 18:51:03 +0800 KubeletHasSufficientMemory kubelet has sufficient memory available

DiskPressure False Fri, 08 Nov 2024 21:32:21 +0800 Thu, 07 Nov 2024 18:51:03 +0800 KubeletHasNoDiskPressure kubelet has no disk pressure

PIDPressure False Fri, 08 Nov 2024 21:32:21 +0800 Thu, 07 Nov 2024 18:51:03 +0800 KubeletHasSufficientPID kubelet has sufficient PID available

Ready True Fri, 08 Nov 2024 21:32:21 +0800 Thu, 07 Nov 2024 18:51:05 +0800 KubeletReady kubelet is posting ready status

Addresses:

InternalIP: 192.168.65.3

Hostname: docker-desktop

Capacity:

cpu: 8

ephemeral-storage: 61202244Ki

hugepages-1Gi: 0

hugepages-2Mi: 0

hugepages-32Mi: 0

hugepages-64Ki: 0

memory: 8127836Ki

pods: 110

Allocatable:

cpu: 8

ephemeral-storage: 56403987978

hugepages-1Gi: 0

hugepages-2Mi: 0

hugepages-32Mi: 0

hugepages-64Ki: 0

memory: 8025436Ki

pods: 110

System Info:

Machine ID: 59d800f3-a762-4db0-ab93-1b30c590c207

System UUID: 59d800f3-a762-4db0-ab93-1b30c590c207

Boot ID: 508e5ff2-6607-48d4-aba3-ed6089d1bf0c

Kernel Version: 6.10.11-linuxkit

OS Image: Docker Desktop

Operating System: linux

Architecture: arm64

Container Runtime Version: docker://27.3.1

Kubelet Version: v1.30.2

Kube-Proxy Version: v1.30.2

Non-terminated Pods: (7 in total)

Namespace Name CPU Requests CPU Limits Memory Requests Memory Limits Age

--------- ---- ------------ ---------- --------------- ------------- ---

kube-system coredns-7db6d8ff4d-dwp9w 100m (1%) 0 (0%) 70Mi (0%) 170Mi (2%) 26h

kube-system coredns-7db6d8ff4d-kh4x9 100m (1%) 0 (0%) 70Mi (0%) 170Mi (2%) 26h

kube-system etcd-docker-desktop 100m (1%) 0 (0%) 100Mi (1%) 0 (0%) 26h

kube-system kube-apiserver-docker-desktop 250m (3%) 0 (0%) 0 (0%) 0 (0%) 26h

kube-system kube-controller-manager-docker-desktop 200m (2%) 0 (0%) 0 (0%) 0 (0%) 26h

kube-system kube-proxy-shvff 0 (0%) 0 (0%) 0 (0%) 0 (0%) 26h

kube-system kube-scheduler-docker-desktop 100m (1%) 0 (0%) 0 (0%) 0 (0%) 26h

Allocated resources:

(Total limits may be over 100 percent, i.e., overcommitted.)

Resource Requests Limits

-------- -------- ------

cpu 850m (10%) 0 (0%)

memory 240Mi (3%) 340Mi (4%)

ephemeral-storage 0 (0%) 0 (0%)

hugepages-1Gi 0 (0%) 0 (0%)

hugepages-2Mi 0 (0%) 0 (0%)

hugepages-32Mi 0 (0%) 0 (0%)

hugepages-64Ki 0 (0%) 0 (0%)

Events:

Type Reason Age From Message

---- ------ ---- ---- -------

Normal Starting 66m kube-proxy

Normal Starting 66m kubelet Starting kubelet.

Normal NodeHasSufficientMemory 66m (x8 over 66m) kubelet Node docker-desktop status is now: NodeHasSufficientMemory

Normal NodeHasNoDiskPressure 66m (x8 over 66m) kubelet Node docker-desktop status is now: NodeHasNoDiskPressure

Normal NodeHasSufficientPID 66m (x7 over 66m) kubelet Node docker-desktop status is now: NodeHasSufficientPID

Normal NodeAllocatableEnforced 66m kubelet Updated Node Allocatable limit across pods

Normal RegisteredNode 66m node-controller Node docker-desktop event: Registered Node docker-desktop in Controller

(base) yufei@MacBook-Pro-2 k8s-docker-desktop-for-mac %

docker attach

上一篇：年轻人谁还用Docker?
下一篇：使用Docker部署nextjs应用

docker -k8s

相关推荐

C# 13 和 .NET 9 全知道 :13 使用 ASP.NET Core 构建网站 (1)

因果推断Matching方式实现代码因果推断模型

git pull命令使用实例 git pull--rebase

面试官:git pull是哪两个指令的组合?

git 执行pull错误如何撤销 git pull fail

git pull 和git fetch 命令分别有什么作用?二者有什么区别?

git fetch 和git pull 的异同 git中fetch和pull的区别

git pull 之后本地代码被覆盖解决方案

还可以这样玩?Git基本原理及各种骚操作，涨知识了

git命令之pull git.pull

docker -k8s

相关推荐

C# 13 和 .NET 9 全知道 :13 使用 ASP.NET Core 构建网站 (1)

因果推断Matching方式实现代码 因果推断模型

git pull命令使用实例 git pull--rebase

面试官:git pull是哪两个指令的组合?

git 执行pull错误如何撤销 git pull fail

git pull 和git fetch 命令分别有什么作用?二者有什么区别?

git fetch 和git pull 的异同 git中fetch和pull的区别

git pull 之后本地代码被覆盖 解决方案

还可以这样玩?Git基本原理及各种骚操作，涨知识了

git命令之pull git.pull

因果推断Matching方式实现代码因果推断模型

git pull 之后本地代码被覆盖解决方案