CaaSP4 - 命令记录

# kubectl describe nodes master01
Name:               master01
Roles:              master
Labels:             beta.kubernetes.io/arch=amd64
                    beta.kubernetes.io/os=linux
                    kubernetes.io/arch=amd64
                    kubernetes.io/hostname=master01
                    kubernetes.io/os=linux
                    node-role.kubernetes.io/master=
Annotations:        io.cilium.network.ipv4-cilium-host: 10.244.0.1
                    io.cilium.network.ipv4-health-ip: 10.244.0.144
                    io.cilium.network.ipv4-pod-cidr: 10.244.0.0/24
                    io.cilium.network.ipv6-cilium-host: f00d::af4:0:0:1
                    io.cilium.network.ipv6-health-ip: f00d::af4:0:0:8ce1
                    io.cilium.network.ipv6-pod-cidr: f00d::af4:0:0:0/96
                    kubeadm.alpha.kubernetes.io/cri-socket: /var/run/crio/crio.sock
                    node.alpha.kubernetes.io/ttl: 0
                    volumes.kubernetes.io/controller-managed-attach-detach: true
CreationTimestamp:  Sun, 06 Oct 2019 16:03:08 +0800
Taints:             node-role.kubernetes.io/master:NoSchedule
Unschedulable:      false
Conditions:
  Type                 Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message
  ----                 ------  -----------------                 ------------------                ------                       -------
  NetworkUnavailable   False   Wed, 09 Oct 2019 09:48:15 +0800   Wed, 09 Oct 2019 09:48:15 +0800   CiliumIsUp                   Cilium is running on this node
  MemoryPressure       False   Wed, 09 Oct 2019 10:41:58 +0800   Sun, 06 Oct 2019 16:03:00 +0800   KubeletHasSufficientMemory   kubelet has sufficient memory available
  DiskPressure         False   Wed, 09 Oct 2019 10:41:58 +0800   Sun, 06 Oct 2019 16:03:00 +0800   KubeletHasNoDiskPressure     kubelet has no disk pressure
  PIDPressure          False   Wed, 09 Oct 2019 10:41:58 +0800   Sun, 06 Oct 2019 16:03:00 +0800   KubeletHasSufficientPID      kubelet has sufficient PID available
  Ready                True    Wed, 09 Oct 2019 10:41:58 +0800   Sun, 06 Oct 2019 16:08:28 +0800   KubeletReady                 kubelet is posting ready status. AppArmor enabled
Addresses:
  InternalIP:  172.200.50.70
  Hostname:    master01
Capacity:
 cpu:                4
 ephemeral-storage:  17394Mi
 hugepages-1Gi:      0
 hugepages-2Mi:      0
 memory:             3746524Ki
 pods:               110
Allocatable:
 cpu:                4
 ephemeral-storage:  16415037823
 hugepages-1Gi:      0
 hugepages-2Mi:      0
 memory:             3644124Ki
 pods:               110
System Info:
 Machine ID:                 21c43aad5388499bba20966cf4aad01a
 System UUID:                e5744d56-fe06-ebb8-779a-ed0dfc4f6e07
 Boot ID:                    bff71ca7-f8d5-40ec-823a-017cda604703
 Kernel Version:             4.12.14-197.18-default
 OS Image:                   SUSE Linux Enterprise Server 15 SP1
 Operating System:           linux
 Architecture:               amd64
 Container Runtime Version:  cri-o://1.15.0
 Kubelet Version:            v1.15.2
 Kube-Proxy Version:         v1.15.2
PodCIDR:                     10.244.0.0/24
Non-terminated Pods:         (9 in total)
  Namespace                  Name                                CPU Requests  CPU Limits  Memory Requests  Memory Limits  AGE
  ---------                  ----                                ------------  ----------  ---------------  -------------  ---
  kube-system                cilium-d6krt                        0 (0%)        0 (0%)      0 (0%)           0 (0%)         2d18h
  kube-system                coredns-69c4947958-jq5fj            100m (2%)     0 (0%)      70Mi (1%)        170Mi (4%)     2d18h
  kube-system                coredns-69c4947958-m29fz            100m (2%)     0 (0%)      70Mi (1%)        170Mi (4%)     2d18h
  kube-system                etcd-master01                       0 (0%)        0 (0%)      0 (0%)           0 (0%)         2d18h
  kube-system                kube-apiserver-master01             250m (6%)     0 (0%)      0 (0%)           0 (0%)         2d18h
  kube-system                kube-controller-manager-master01    200m (5%)     0 (0%)      0 (0%)           0 (0%)         2d18h
  kube-system                kube-proxy-2f57p                    0 (0%)        0 (0%)      0 (0%)           0 (0%)         2d18h
  kube-system                kube-scheduler-master01             100m (2%)     0 (0%)      0 (0%)           0 (0%)         2d18h
  kube-system                kured-5vhdw                         0 (0%)        0 (0%)      0 (0%)           0 (0%)         2d18h
Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted.)
  Resource           Requests    Limits
  --------           --------    ------
  cpu                750m (18%)  0 (0%)
  memory             140Mi (3%)  340Mi (9%)
  ephemeral-storage  0 (0%)      0 (0%)
Events:
  Type     Reason                   Age                From                  Message
  ----     ------                   ----               ----                  -------
  Normal   Starting                 54m                kubelet, master01     Starting kubelet.
  Normal   NodeHasSufficientMemory  54m (x8 over 54m)  kubelet, master01     Node master01 status is now: NodeHasSufficientMemory
  Normal   NodeHasNoDiskPressure    54m (x8 over 54m)  kubelet, master01     Node master01 status is now: NodeHasNoDiskPressure
  Normal   NodeHasSufficientPID     54m (x7 over 54m)  kubelet, master01     Node master01 status is now: NodeHasSufficientPID
  Normal   NodeAllocatableEnforced  54m                kubelet, master01     Updated Node Allocatable limit across pods
  Warning  readOnlySysFS            54m                kube-proxy, master01  CRI error: /sys is read-only: cannot modify conntrack limits, problems may arise later (If running Docker, see docker issue #24000)
  Normal   Starting                 54m                kube-proxy, master01  Starting kube-proxy.

原文地址：https://www.cnblogs.com/alfiesuse/p/11640348.html

时间： 2024-10-16 00:56:30

CaaSP4 - 命令记录的相关文章

CentOS7设置开放端口以及常用的命令记录

CentOS7与以前常用的CentOS6还是有一些不同之处的,比如在设置开放端口的时候稍许有些不同,常用的iptables命令已经被 firewalld代替.这几天正好有在CentOS7系统中玩Seafile自建网盘,默认的时候是没有开启8082端口的,然后看到CentOS7开 放端口稍微与CentOS6不同,这里本着学习和记录的习惯,将CentOS7开放端口以及常用的使用命令记录整理. 这样在以后遇到有需要CentOS7开放端口和命令的时候直接翻阅使用到,内容比较基础,对于大佬来说简单,但是我

AIX LVM 常用命令记录

针对物理卷的操作指令 lsdev--列出ODM中的设备 chdev--修改一个AIX设备的属性 mkdev--创建一个AIX设备 chpv--修改物理卷的状态和属性 lspv--查看AIX中物理卷的相关信息 migratepv--将一个物理卷中的物理分区(数据)迁移到另一个物理卷   针对卷组的操作指令 mkvg--创建新卷组 extendvg--扩展vg reducevg--缩小vg chvg--修改卷组的属性 lsvg--查看卷组的相关信息 importvg--导入vg到AIX系统中 exp

清除Centos系统用户登录记录和命令记录

echo > /var/log/wtmp #清除用户登录记录和命令记录 echo > /var/log/btmp echo > /var/log/secure #如果没有这个文件,重启syslog进程service syslog restart echo > .bash_history history -c #清除命令记录

Bash shell命令记录和CentOS的一些技巧

①CentOS的实用技巧: 一.按下ctrl+alt+F2可由图形界面切换至命令行(shell窗口),按下ctrl+alt+F1可由命令行切换至图形界面(前提是安装CentOS时软件选择项选择安装了图形界面,一般是GNOME) ②shell命令记录: 一.ifconfig命令是Linux中用于显示或配置网络设备的命令,英文全称是network interfaces configuring.配置网卡的IP地址语法例:ifconfig eth0 192.168.0.1 netmask 255.255

二十七、Linux下常用的shell命令记录

本文章记录我在linux系统下常用或有用的系统级命令,包括软硬件查看.修改命令,有CPU.内存.硬盘.网络.系统管理等命令.但本文不打算介绍生僻命令,也不介绍各个linux发行版下的特有命令,且以后会持续更新. 说明,我是在一个Centos 6.4 64位的虚拟机系统进行测试.本文介绍的命令都会在此Centos下运行验证(也有部分命令会在我的suse/ubuntu系统里测试的,会做特明说明),但运行结果就不再列出了. 硬件篇 CPU相关 lscpu #查看的是cpu的统计信息. cat /pro

Redis-常用命令记录

清空数据命令: 旧版本:#redis-cli -h 10.133.212.173 keys "*"| xargs redis-cli del 新版本: # redis-cli -h 10.133.212.32 10.133.212.32:6379> flushall [此处是清空所有DB,FLUSHDB清空指定DB数据] OK 10.133.212.32:6379> keys * (empty list or set) Redis-常用命令记录

Linux以及Android开发中的小技巧和长繁命令记录收集

不断更新收集中.... 2014071743 ssh以nx_guest的身份登录到172.24.221.137,然后在172.24.221.137与172.24.61.252的8080端口建立网络连接,同时创建端口为5678的本地代理服务 ssh -C -f -N -o 'TCPKeepAlive=yes' -L 5678:172.24.61.252:8080 [email protected] 反编译android下的二进制程序 ./prebuilts/gcc/linux-x86/arm/ar

简易的git命令记录

看状态 >>git status 看修改 >>git diff 提交到暂存区 >>git add .(全部提交,也可以用文件名) 暂存区内容提交到分支 >>git commit -m '***'(说明) 看提交log >>git log 看命令记录 >>git reflog 版本回退(head表示当前版本,一个^表示退回一个版本,退回100个可以用head~100) >>git reset --hard head^ 版本前

mysql-mmm常用命令记录

常用命令记录: vim /etc/mysql-mmm/mmm_common.conf vim /var/log/mysql-mmm/mmm_mond.log monitor: service mysql-mmm-monitor start/stop/restart agent: service mysql-mmm-agent start/stop/restart mysql-mmm有6种状态 1.online 2.admin_offline 3.hard_offline 4.awaiting_r