运行 kubectl exec 时禁用 Kubernetes 上的网络日志答案

【问题标题】：Disabling network logs on Kubernetes when running kubectl exec运行 kubectl exec 时禁用 Kubernetes 上的网络日志
【发布时间】：2017-08-25 23:16:40
【问题描述】：

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 还是我的环境。

【问题讨论】：

不起作用:(
前一个不正确，试试kubectl exec -it <PODNAME> -- /bin/bash > /dev/null 2>&1
哼它真的打破了我的外壳 :p 没有任何反应了

标签： bash logging kubernetes kubernetes-go-client

【解决方案1】：

刚刚找到： unset DEBUG 已修复！

【讨论】：

我在 pod 内设置了这个。但实际上我们必须将它设置在我们正在运行的**主机&&（您的机器）中kubectl exec

【解决方案2】：

如果你在 cmd 运行：

set DEBUG=

如果你在 powershell 中：

$env:DEBUG=""

如果你是一个类似 bash 的 shell：

export DEBUG= 或 unset DEBUG

【讨论】：