[root@t-middle01 ~]# brctl addbr mybr [root@t-middle01 ~]# brctl show bridge name bridge id STP enabled interfaces mybr 8000.000000000000 no
通过addbr创建一个名为mybr的网桥。通过show命令可以看一下。现在网桥还没有连接任何网卡。
创建一对veth
我们创建一对veth,然后挂到网桥上
1 2 3
[root@t-middle01 ~]# ip link add veth0 type veth peer name veth1 [root@t-middle01 ~]# ifconfig veth0 1.2.3.100/24 up [root@t-middle01 ~]# ifconfig veth1 1.2.3.200/24 up
# brctl show bridge name bridge id STP enabled interfaces docker0 8000.02421e0d1279 no
因为还没有启动任何容器,所以interfaces没有任何网卡。
1 2 3 4 5
# docker run --name busybox -itd busybox e10df4d10de378d6b2db16d9ea5a3f9fb62294d2b9ba89df08f549c37b2769a6 # brctl show bridge name bridge id STP enabled interfaces docker0 8000.02421e0d1279 no veth066ee4f
# velero backup logs backup-all-20230410170007 Logs for backup "backup-all-20230410170007" are not available until it's finished processing. Please wait until the backup has a phase of Completed or Failed and try again.
发现只有完成的或失败的,才能看日志,InProgress状态的不能查看日志
看一下velero的pod的日志
1
kubectl -n velero logs velero-84c6fd74dc-q7gph
全是info日志,没有看出什么
然后describe一下pod看看
1
kubectl -n velero describe pod velero-84c6fd74dc-q7gph
Warning FailedScheduling <unknown> default-scheduler 0/5 nodes are available: 1 node(s) had taints that the pod didn't tolerate, 1 node(s) were unschedulable, 3 node(s) had volume node affinity conflict.
node上有volume的节点亲和性冲突。
那么去看看看这个pv有什么清河县的配置
1
kubectl -n kubesphere-monitoring-system get pod prometheus-k8s-0 -o yaml