bash – 在运行kubectl exec时禁用Kubernetes上的网络日志

发布时间：2020-12-15 22:38:23 所属栏目：安全来源：网络整理

导读：Runnning kubectl exec -it PODNAME – / bin / bash正在打印??很多 shell的垃圾： ) Data frame handling I0331 17:46:15.486652 3807 logs.go:41] (0xc4201158c0) Data frame received for 5 I0331 17:46:15.486671 3807 logs.go:41] (0xc42094a000) (5) D

Runnning kubectl exec -it< PODNAME> – / bin / bash正在打印??很多 shell的垃圾：

) Data frame handling
                     I0331 17:46:15.486652    3807 logs.go:41] (0xc4201158c0) Data frame received for 5
                                                                                                       I0331 17:46:15.486671    3807 logs.go:41] (0xc42094a000) (5) Data frame handling
                                                                                                                                                                                       I0331 17:46:15.486682    3807 logs.go:41] (0xc42094a000) (5) Data frame sent
                                                                                                                                                                                                                                                                   root@hello-node-2399519400-6q6s3:/# I0331 17:46:16.667823    3807 logs.go:41] (0xc420687680) (3) Writing data frame
                                                  I0331 17:46:16.669223    3807 logs.go:41] (0xc4201158c0) Data frame received for 5
                                                                                                                                    I0331 17:46:16.669244    3807 logs.go:41] (0xc42094a000) (5) Data frame handling
                                                                                                                                                                                                                    I0331 17:46:16.669254    3807 logs.go:41] (0xc42094a000) (5) Data frame sent

root@hello-node-2399519400-6q6s3:/# I0331 17:46:17.331753    3807 logs.go:41] (0xc420687680) (3) Writing data frame
                                                                                                                   I0331 17:46:17.333338    3807 logs.go:41] (0xc4201158c0) Data frame received for 5
                                                                                                                                                                                                     I0331 17:46:17.333358    3807 logs.go:41] (0xc42094a000) (5) Data frame handling
                                                                                                                                                                                                                                                                                     I0331 17:46:17.333369    3807 logs.go:41] (0xc42094a000) (5) Data frame sent

I0331 17:46:17.333922    3807 logs.go:41] (0xc4201158c0) Data frame received for 5
                                                                                  I0331 17:46:17.333943    3807 logs.go:41] (0xc42094a000) (5) Data frame handling
                                                                                                                                                                  I0331 17:46:17.333956    3807 logs.go:41] (0xc42094a000) (5) Data frame sent
                                                                                                                                                                                                                                              root@hello-node-2399519400-6q6s3:/# I0331 17:46:17.738444    3807 logs.go:41] (0xc420687680) (3) Writing data frame
                             I0331 17:46:17.740563    3807 logs.go:41] (0xc4201158c0) Data frame received for 5
                                                                                                               I0331 17:46:17.740591    3807 logs.go:41] (0xc42094a000) (5) Data frame handling
                                                                                                                                                                                               I0331 17:46:17.740606    3807 logs.go:41] (0xc42094a000) (5) Data frame sent

没有’t’选项会更好一些：

kubectl exec -i hello-4103519535-hcdm6 -- /bin/bash
I0331 18:29:06.918584    4992 logs.go:41] (0xc4200878c0) (0xc4204c5900) Create stream
I0331 18:29:06.918714    4992 logs.go:41] (0xc4200878c0) (0xc4204c5900) Stream added,broadcasting: 1
I0331 18:29:06.928571    4992 logs.go:41] (0xc4200878c0) Reply frame received for 1
I0331 18:29:06.928605    4992 logs.go:41] (0xc4200878c0) (0xc4203ffc20) Create stream
I0331 18:29:06.928614    4992 logs.go:41] (0xc4200878c0) (0xc4203ffc20) Stream added,broadcasting: 3
I0331 18:29:06.930565    4992 logs.go:41] (0xc4200878c0) Reply frame received for 3
I0331 18:29:06.930603    4992 logs.go:41] (0xc4200878c0) (0xc4204c59a0) Create stream
I0331 18:29:06.930615    4992 logs.go:41] (0xc4200878c0) (0xc4204c59a0) Stream added,broadcasting: 5
I0331 18:29:06.932455    4992 logs.go:41] (0xc4200878c0) Reply frame received for 5
I0331 18:29:06.932499    4992 logs.go:41] (0xc4200878c0) (0xc420646000) Create stream
I0331 18:29:06.932511    4992 logs.go:41] (0xc4200878c0) (0xc420646000) Stream added,broadcasting: 7
I0331 18:29:06.935363    4992 logs.go:41] (0xc4200878c0) Reply frame received for 7
echo toto
I0331 18:29:08.943066    4992 logs.go:41] (0xc4203ffc20) (3) Writing data frame
I0331 18:29:08.947811    4992 logs.go:41] (0xc4200878c0) Data frame received for 5
I0331 18:29:08.947837    4992 logs.go:41] (0xc4204c59a0) (5) Data frame handling
I0331 18:29:08.947851    4992 logs.go:41] (0xc4204c59a0) (5) Data frame sent
toto

有没有办法禁用它？
它会来自我的环境吗？
我仍然不确定它是否来自Kubernetes或我的环境.

解决方法

刚发现它： unset DEBUG修复了它！

（编辑：李大同）

【声明】本站内容均来自网络，其相关言论仅代表作者个人观点，不代表本站立场。若无意侵犯到您的权利，请及时与联系站长删除相关内容!