最近研究OpenShift virtulization, 各种Pod对KVM进程的封装，引发了Pod中进程到底在Node中是什么表现形势的好奇，因为对基础知识的不扎实，还是希望找个环境能仔细看看，建立起openshift 4.12的环境后，首先列出某个节点上的所有的Pod

[lab-user@bastion ~]$ oc get pods -A --field-selector=spec.host=ip-10-0-148-57.us-east-2.compute.internal

NAMESPACE                                NAME                                                     READY   STATUS      RESTARTS      AGE

openshift-cluster-csi-drivers            aws-ebs-csi-driver-node-c4ddr                            3/3     Running     0             46m

openshift-cluster-node-tuning-operator   tuned-5lrjg                                              1/1     Running     0             46m

openshift-console                        downloads-595667555c-477b2                               1/1     Running     0             39m

openshift-debug-b7f7z                    ip-10-0-148-57.us-east-2.compute.internal-debug          1/1     Running     0             22m

openshift-dns                            dns-default-cxr55                                        2/2     Running     0             45m

openshift-dns                            node-resolver-szmvw                                      1/1     Running     0             46m

openshift-image-registry                 image-registry-6945b97db4-gnjfl                          1/1     Running     0             44m

openshift-image-registry                 node-ca-56rgw                                            1/1     Running     0             44m

openshift-ingress-canary                 ingress-canary-7twkk                                     1/1     Running     0             44m

openshift-ingress                        router-default-74f6d94f48-cwczb                          1/1     Running     0             30m

openshift-machine-config-operator        machine-config-daemon-fgchf                              2/2     Running     0             46m

openshift-monitoring                     alertmanager-main-1                                      6/6     Running     1 (39m ago)   39m

openshift-monitoring                     node-exporter-w8f5k                                      2/2     Running     0             44m

openshift-monitoring                     prometheus-adapter-b87c6d546-7jlzw                       1/1     Running     0             39m

openshift-monitoring                     prometheus-k8s-1                                         6/6     Running     0             39m

openshift-monitoring                     prometheus-operator-admission-webhook-566d9cc57c-mfwc8   1/1     Running     0             52m

openshift-monitoring                     thanos-querier-7dcb8856d-d8g8t                           6/6     Running     0             39m

openshift-multus                         multus-8cgln                                             1/1     Running     0             46m

openshift-multus                         multus-additional-cni-plugins-cpdbf                      1/1     Running     0             46m

openshift-multus                         network-metrics-daemon-5rjqw                             2/2     Running     0             46m

openshift-network-diagnostics            network-check-source-6655898df9-p9qjz                    1/1     Running     0             54m

openshift-network-diagnostics            network-check-target-5qlvj                               1/1     Running     0             46m

openshift-operator-lifecycle-manager     collect-profiles-28103550-nrvlz                          0/1     Completed   0             40m

openshift-operator-lifecycle-manager     collect-profiles-28103565-lt2ct                          0/1     Completed   0             28m

openshift-operator-lifecycle-manager     collect-profiles-28103580-nwh94                          0/1     Completed   0             13m

openshift-ovn-kubernetes                 ovnkube-node-p4dld                                       5/5     Running     0             46m

以prometheus-adapter-xxxx为例，登录进去查看一下Pod里面运行的进程

[lab-user@bastion ~]$ oc project openshift-monitoring

Already on project "openshift-monitoring" on server "https://api.cluster-gmwqp.gmwqp.sandbox1496.opentlc.com:6443".

[lab-user@bastion ~]$ oc rsh prometheus-adapter-b87c6d546-7jlzw

sh-4.4$ ps -ef

UID          PID    PPID  C STIME TTY          TIME CMD

1000430+       1       0  0 08:34 ?        00:00:13 /usr/bin/adapter --prometheus-auth-config=/etc/prometheus-config/prometheus-config.yaml --config=/etc/adapter/config.yaml --logtostderr=

1000430+      37       0  1 09:15 pts/0    00:00:00 /bin/sh

1000430+      43      37  0 09:15 pts/0    00:00:00 ps -ef

比较简单，只有一个，然后登陆到节点查看相关进程

sh-4.4# ps -ef | grep prometheus-adapter

root       11677       1  0 08:34 ?        00:00:00 /usr/bin/conmon -b /run/containers/storage/overlay-containers/1961af83ec2bf15ae89371edd5ebb534886c9db6bfaa385ac4fb53b4232df966/userdata -c 1961af83ec2bf15ae89371edd5ebb534886c9db6bfaa385ac4fb53b4232df966 --exit-dir /var/run/crio/exits -l /var/log/pods/openshift-monitoring_prometheus-adapter-b87c6d546-7jlzw_18617999-d875-40e2-b29f-c40743f8314b/prometheus-adapter/0.log --log-level info -n k8s_prometheus-adapter_prometheus-adapter-b87c6d546-7jlzw_openshift-monitoring_18617999-d875-40e2-b29f-c40743f8314b_0 -P /run/containers/storage/overlay-containers/1961af83ec2bf15ae89371edd5ebb534886c9db6bfaa385ac4fb53b4232df966/userdata/conmon-pidfile -p /run/containers/storage/overlay-containers/1961af83ec2bf15ae89371edd5ebb534886c9db6bfaa385ac4fb53b4232df966/userdata/pidfile --persist-dir /var/lib/containers/storage/overlay-containers/1961af83ec2bf15ae89371edd5ebb534886c9db6bfaa385ac4fb53b4232df966/userdata -r /usr/bin/runc --runtime-arg --root=/run/runc --socket-dir-path /var/run/crio --syslog -u 1961af83ec2bf15ae89371edd5ebb534886c9db6bfaa385ac4fb53b4232df966 -s

root       64634   35507  0 09:16 pts/1    00:00:00 grep prometheus-adapter

可见Pod里面的进程和Nodes上的进程是一对一的关系，我们再找一个多进程的，比如prometheus-k8s-1

因为rsh进入pod以后发现没有ps,那么我们登录节点看看

sh-4.4# crictl ps | grep prometheus-k8s-1

1b1d29d044d4f       8dd80e25afda5c9466a26ef90346b419a8cc9840bd8b553257a0c6df2c5bac6c                                                         42 minutes ago      Running             kube-rbac-proxy-thanos                  0                   9d74de5a22175       prometheus-k8s-1

bacbcddd17d2c       8dd80e25afda5c9466a26ef90346b419a8cc9840bd8b553257a0c6df2c5bac6c                                                         42 minutes ago      Running             kube-rbac-proxy                         0                   9d74de5a22175       prometheus-k8s-1

22d9f341cb2b9       e1f27569f2e6745ac23c33e89b8e569069970ab56a54114e93f6a31570b86334                                                         42 minutes ago      Running             prometheus-proxy                        0                   9d74de5a22175       prometheus-k8s-1

a36c49e125c9a       4efdbf6a731d2feb217ecd0fb0d792dcadf854e826d4db235cafc0268b2621d4                                                         42 minutes ago      Running             thanos-sidecar                          0                   9d74de5a22175       prometheus-k8s-1

76140a26677b1       c9868e04bec41eda58502d70bacc3f2cb5084f5d643b76fb018e3076f7d38014                                                         42 minutes ago      Running             config-reloader                         0                   9d74de5a22175       prometheus-k8s-1

2b0aa6f218f55       quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:97ffae63353c694fe66615679429351a96711cbdeb400555181dea8688a388ea   42 minutes ago      Running             prometheus   

sh-4.4# crictl ps | grep prometheus-k8s-1 | wc -l

6

然后通过ps查看

sh-4.4# ps -ef | grep prometheus-k8s-1

root       12918       1  0 08:34 ?        00:00:00 /usr/bin/conmon -b /run/containers/storage/overlay-containers/2b0aa6f218f552f0d1009b07a80d23d9d47c8b63c23777fb51dcb1aa648d0316/userdata -c 2b0aa6f218f552f0d1009b07a80d23d9d47c8b63c23777fb51dcb1aa648d0316 --exit-dir /var/run/crio/exits -l /var/log/pods/openshift-monitoring_prometheus-k8s-1_0a15cd78-757d-4322-9f35-94f7c42860b4/prometheus/0.log --log-level info -n k8s_prometheus_prometheus-k8s-1_openshift-monitoring_0a15cd78-757d-4322-9f35-94f7c42860b4_0 -P /run/containers/storage/overlay-containers/2b0aa6f218f552f0d1009b07a80d23d9d47c8b63c23777fb51dcb1aa648d0316/userdata/conmon-pidfile -p /run/containers/storage/overlay-containers/2b0aa6f218f552f0d1009b07a80d23d9d47c8b63c23777fb51dcb1aa648d0316/userdata/pidfile --persist-dir /var/lib/containers/storage/overlay-containers/2b0aa6f218f552f0d1009b07a80d23d9d47c8b63c23777fb51dcb1aa648d0316/userdata -r /usr/bin/runc --runtime-arg --root=/run/runc --socket-dir-path /var/run/crio --syslog -u 2b0aa6f218f552f0d1009b07a80d23d9d47c8b63c23777fb51dcb1aa648d0316 -s

root       12978       1  0 08:34 ?        00:00:00 /usr/bin/conmon -b /run/containers/storage/overlay-containers/76140a26677b1512e18864b5c1bfb31a2847d581721a64cd7f7633fb2a62ab66/userdata -c 76140a26677b1512e18864b5c1bfb31a2847d581721a64cd7f7633fb2a62ab66 --exit-dir /var/run/crio/exits -l /var/log/pods/openshift-monitoring_prometheus-k8s-1_0a15cd78-757d-4322-9f35-94f7c42860b4/config-reloader/0.log --log-level info -n k8s_config-reloader_prometheus-k8s-1_openshift-monitoring_0a15cd78-757d-4322-9f35-94f7c42860b4_0 -P /run/containers/storage/overlay-containers/76140a26677b1512e18864b5c1bfb31a2847d581721a64cd7f7633fb2a62ab66/userdata/conmon-pidfile -p /run/containers/storage/overlay-containers/76140a26677b1512e18864b5c1bfb31a2847d581721a64cd7f7633fb2a62ab66/userdata/pidfile --persist-dir /var/lib/containers/storage/overlay-containers/76140a26677b1512e18864b5c1bfb31a2847d581721a64cd7f7633fb2a62ab66/userdata -r /usr/bin/runc --runtime-arg --root=/run/runc --socket-dir-path /var/run/crio --syslog -u 76140a26677b1512e18864b5c1bfb31a2847d581721a64cd7f7633fb2a62ab66 -s

root       13037       1  0 08:34 ?        00:00:00 /usr/bin/conmon -b /run/containers/storage/overlay-containers/a36c49e125c9a385e8e32e904e61c404c40135a1c5040d01244692e1a930f730/userdata -c a36c49e125c9a385e8e32e904e61c404c40135a1c5040d01244692e1a930f730 --exit-dir /var/run/crio/exits -l /var/log/pods/openshift-monitoring_prometheus-k8s-1_0a15cd78-757d-4322-9f35-94f7c42860b4/thanos-sidecar/0.log --log-level info -n k8s_thanos-sidecar_prometheus-k8s-1_openshift-monitoring_0a15cd78-757d-4322-9f35-94f7c42860b4_0 -P /run/containers/storage/overlay-containers/a36c49e125c9a385e8e32e904e61c404c40135a1c5040d01244692e1a930f730/userdata/conmon-pidfile -p /run/containers/storage/overlay-containers/a36c49e125c9a385e8e32e904e61c404c40135a1c5040d01244692e1a930f730/userdata/pidfile --persist-dir /var/lib/containers/storage/overlay-containers/a36c49e125c9a385e8e32e904e61c404c40135a1c5040d01244692e1a930f730/userdata -r /usr/bin/runc --runtime-arg --root=/run/runc --socket-dir-path /var/run/crio --syslog -u a36c49e125c9a385e8e32e904e61c404c40135a1c5040d01244692e1a930f730 -s

root       13087       1  0 08:34 ?        00:00:00 /usr/bin/conmon -b /run/containers/storage/overlay-containers/22d9f341cb2b9f8748852a5b83146844cebb8ec2e4e00ce17016d523f5edb1ec/userdata -c 22d9f341cb2b9f8748852a5b83146844cebb8ec2e4e00ce17016d523f5edb1ec --exit-dir /var/run/crio/exits -l /var/log/pods/openshift-monitoring_prometheus-k8s-1_0a15cd78-757d-4322-9f35-94f7c42860b4/prometheus-proxy/0.log --log-level info -n k8s_prometheus-proxy_prometheus-k8s-1_openshift-monitoring_0a15cd78-757d-4322-9f35-94f7c42860b4_0 -P /run/containers/storage/overlay-containers/22d9f341cb2b9f8748852a5b83146844cebb8ec2e4e00ce17016d523f5edb1ec/userdata/conmon-pidfile -p /run/containers/storage/overlay-containers/22d9f341cb2b9f8748852a5b83146844cebb8ec2e4e00ce17016d523f5edb1ec/userdata/pidfile --persist-dir /var/lib/containers/storage/overlay-containers/22d9f341cb2b9f8748852a5b83146844cebb8ec2e4e00ce17016d523f5edb1ec/userdata -r /usr/bin/runc --runtime-arg --root=/run/runc --socket-dir-path /var/run/crio --syslog -u 22d9f341cb2b9f8748852a5b83146844cebb8ec2e4e00ce17016d523f5edb1ec -s

root       13142       1  0 08:34 ?        00:00:00 /usr/bin/conmon -b /run/containers/storage/overlay-containers/bacbcddd17d2cfd032c0e890783018bec8d98a06b373918576b0de533332b369/userdata -c bacbcddd17d2cfd032c0e890783018bec8d98a06b373918576b0de533332b369 --exit-dir /var/run/crio/exits -l /var/log/pods/openshift-monitoring_prometheus-k8s-1_0a15cd78-757d-4322-9f35-94f7c42860b4/kube-rbac-proxy/0.log --log-level info -n k8s_kube-rbac-proxy_prometheus-k8s-1_openshift-monitoring_0a15cd78-757d-4322-9f35-94f7c42860b4_0 -P /run/containers/storage/overlay-containers/bacbcddd17d2cfd032c0e890783018bec8d98a06b373918576b0de533332b369/userdata/conmon-pidfile -p /run/containers/storage/overlay-containers/bacbcddd17d2cfd032c0e890783018bec8d98a06b373918576b0de533332b369/userdata/pidfile --persist-dir /var/lib/containers/storage/overlay-containers/bacbcddd17d2cfd032c0e890783018bec8d98a06b373918576b0de533332b369/userdata -r /usr/bin/runc --runtime-arg --root=/run/runc --socket-dir-path /var/run/crio --syslog -u bacbcddd17d2cfd032c0e890783018bec8d98a06b373918576b0de533332b369 -s

root       13194       1  0 08:34 ?        00:00:00 /usr/bin/conmon -b /run/containers/storage/overlay-containers/1b1d29d044d4fadd61fdc8b3e040c4aaa9a8fb2690cffb562d170d3952dbc9d6/userdata -c 1b1d29d044d4fadd61fdc8b3e040c4aaa9a8fb2690cffb562d170d3952dbc9d6 --exit-dir /var/run/crio/exits -l /var/log/pods/openshift-monitoring_prometheus-k8s-1_0a15cd78-757d-4322-9f35-94f7c42860b4/kube-rbac-proxy-thanos/0.log --log-level info -n k8s_kube-rbac-proxy-thanos_prometheus-k8s-1_openshift-monitoring_0a15cd78-757d-4322-9f35-94f7c42860b4_0 -P /run/containers/storage/overlay-containers/1b1d29d044d4fadd61fdc8b3e040c4aaa9a8fb2690cffb562d170d3952dbc9d6/userdata/conmon-pidfile -p /run/containers/storage/overlay-containers/1b1d29d044d4fadd61fdc8b3e040c4aaa9a8fb2690cffb562d170d3952dbc9d6/userdata/pidfile --persist-dir /var/lib/containers/storage/overlay-containers/1b1d29d044d4fadd61fdc8b3e040c4aaa9a8fb2690cffb562d170d3952dbc9d6/userdata -r /usr/bin/runc --runtime-arg --root=/run/runc --socket-dir-path /var/run/crio --syslog -u 1b1d29d044d4fadd61fdc8b3e040c4aaa9a8fb2690cffb562d170d3952dbc9d6 -s

root       69497   35507  0 09:20 pts/1    00:00:00 grep prometheus-k8s-1

sh-4.4# ps -ef | grep prometheus-k8s-1  | wc -l

7

所以基本是对映关系。

关于为什么是通过conmon把容器运行起来，以及整体的架构大家可以去参考cri-o的官网和整个过程

https://cri-o.io/

关于Pod中进程在节点中的研究的更多相关文章

  1. 解析xml文件，遍历输出xml文件中的所有节点， 最终模仿实现struts2框架自动封装参数的功能

    程序结构:src文件夹下存放xml文件 该文件内容: <?xml version="1.0" encoding="UTF-8"?> <myst ...

  2. K8s Scheduler 在调度 pod 过程中遗漏部分节点的问题排查

    问题现象 在TKE控制台上新建版本为v1.18.4(详细版本号 < v1.18.4-tke.5)的独立集群,其中,集群的节点信息如下: 有3个master node和1个worker node, ...

  3. 对Linux0.11 中 进程0 和 进程1分析

    1. 背景 进程的创建过程无疑是最重要的操作系统处理过程之一,很多书和教材上说的最多的还是一些原理的部分,忽略了很多细节.比如,子进程复制父进程所拥有的资源,或者子进程和父进程共享相同的物理页面,拥有 ...

  4. MySQL中双NDBD节点Cluster快速配置

    是MySQL适合于分布式计算环境的高实用.高冗余版本.它采用了NDB Cluster 存储引擎,允许在1个 Cluster 中运行多个MySQL服务器.在MyQL 5.0及以上的二进制版本中.以及与最 ...

  5. C# .Net 多进程同步 通信 共享内存 内存映射文件 Memory Mapped 转 VC中进程与进程之间共享内存 .net环境下跨进程、高频率读写数据 使用C#开发Android应用之WebApp 分布式事务之消息补偿解决方案

    C# .Net 多进程同步 通信 共享内存 内存映射文件 Memory Mapped 转 节点通信存在两种模型:共享内存(Shared memory)和消息传递(Messages passing). ...

  6. 【Azure微服务 Service Fabric 】在SF节点中开启Performance Monitor及设置抓取进程的方式

    前提条件 当我们观察到SF中某一个节点出现CPU不正常的情况,但是由于不能肉眼长期观察,所以可以通过开启Performance Monitor的方式来获取每一个进程的%Processer Time的方 ...

  7. [LeetCode] Inorder Successor in BST 二叉搜索树中的中序后继节点

    Given a binary search tree and a node in it, find the in-order successor of that node in the BST. No ...

  8. OSG中找到特定节点的方法

    OSG中找到特定节点的方法 转自:http://38288890.blog.163.com/blog/static/19612845320072721549504/ 为了在OSG中找到需要的节点并对节 ...

  9. C#读取Appconfig中自定义的节点

    今天在使用Nlog的时候,发现了一个之前没注意的问题. 以前,我的app配置文件都是这么写的,当然配置比较多的时候会改用xml. 如果<appSettings>节点中的内容很多的话,我自己 ...

  10. jackson中JSON字符串节点遍历和修改

    有些场景下,在实现一些基础服务和拦截器的时候,我们可能需要在不知道JSON字符串所属对象类型的情况下,对JSON字符串中的某些属性进行遍历和修改,比如,设置或查询一些报文头字段. 在jackson中, ...

随机推荐

  1. （原创）【B4A】一步一步入门09：xCustomListView，加强版列表、双行带图片、复选框按钮等自定义列表项（控件篇05）

    一.前言 上篇((原创)[B4A]一步一步入门08:ListView,列表.单行.双行.双行带图片.列表项样式(控件篇04))我们讲了ListView,目前官方已经不推荐再使用ListView了,而是 ...

  2. 使用Electron-packager打包已有的web项目，发布客户端

    1.先拉electron代码 git clone https://github.com/electron/electron-quick-start 2.将web项目拷贝到electron-quick- ...

  3. Flutter中如何取消任务

    前言 在开发过程中,取消需求是很常见的,但很容易被忽略.然而,取消需求的好处也很大.例如,在页面中会发送很多请求.如果页面被切走并处于不可见状态,就需要取消未完成的请求任务.如果未及时取消,则可能会导 ...

  4. [Linux/JSON]JSON美化工具:json_pp / jq

    json_pp (git-bash内置的用于JSON格式化的管道工具:默认支持) (Linux CentOS7 暂不支持) curl http://localhost:8080/xxxx.json | ...

  5. vue高阶函数

    <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8&quo ...

  6. Go语言实现基于TCP的内存缓存服务

    接上文: https://www.cnblogs.com/N3ptune/p/16623738.html HTTP/REST的解析导致基于HTTP的内存缓存服务性能不佳,本次实现一个基于TCP的缓存服 ...

  7. vue-element-admin 动态菜单改造

    vue-element-admin 动态菜单改造 vue-element-admin 是一款优秀后台前端解决方案,它基于 vue 和 element-ui实现.开源后台管理系统解决方案项目 Boot- ...

  8. Simulation-计算统计-随机数生成

    library('ggplot2') library('dplyr') Lecture 6 Methods for generating random numbers Goal: Use U(0, 1 ...

  9. springboot mybatis 动态调用oracle存储过程，通过存储过程名称，就能动态调用存储过程、java动态调用oracle存储过程

    由于在开发业务时,可能同时调用的存储过程不知道参数,但是参数从界面.或已经存储在数据库的获取,所以就不希望手动写存储过程的参数,通过简化的调用. 能不能写个动态的业务,只输入存储过程名称,自动获取存储 ...

  10. python数据可视化神库：Matplotlib快速入门

    Matplotlib易于使用,是Python中了不起的可视化库.它建立在NumPy数组的基础上,旨在与更广泛的SciPy堆栈一起工作,并由几个图组成:线图.条形图.散点图.直方图等. 快速入门 imp ...