Kube API 伺服器與 ETCD 之間的通訊日誌

Question

我試圖了解集群中的內部通信，例如創建 Pod 時的內部通信。

root@kmaster-0:# kubectl -v=7 -n mynamespace run mypod --image=nginx
I0903 11:01:06.368969  594516 loader.go:372] Config loaded from file:  /root/.kube/config
I0903 11:01:06.372708  594516 round_trippers.go:432] POST https://192.168.178.111:6443/api/v1/namespaces/mynamespace/pods?fieldManager=kubectl-run

kubectl 的詳細輸出顯示發送到 api 伺服器的 http 請求，因此我想檢查 api 伺服器做了什麼，但 api 伺服器的日誌沒有顯示與建立的 pod 或發送到 ETCD 的請求相關的任何內容。日誌僅顯示以下內容

root@kmaster-0:~# kubectl -n kube-system logs kube-apiserver-kmaster-0
I0903 11:00:52.122893       1 clientconn.go:948] ClientConn switching balancer to "pick_first"
I0903 11:00:57.184420       1 controller.go:611] quota admission added evaluator for: namespaces
I0903 11:01:27.124960       1 client.go:360] parsed scheme: "passthrough"
I0903 11:01:27.125577       1 passthrough.go:48] ccResolverWrapper: sending update to cc: {[{https://127.0.0.1:2379  <nil> 0 <nil>}] <nil> <nil>}
I0903 11:01:27.125838       1 clientconn.go:948] ClientConn switching balancer to "pick_first"
I0903 11:02:11.820307       1 client.go:360] parsed scheme: "passthrough"
I0903 11:02:11.820465       1 passthrough.go:48] ccResolverWrapper: sending update to cc: {[{https://127.0.0.1:2379  <nil> 0 <nil>}] <nil> <nil>}
I0903 11:02:11.820892       1 clientconn.go:948] ClientConn switching balancer to "pick_first"
I0903 11:02:42.852719       1 client.go:360] parsed scheme: "passthrough"
I0903 11:02:42.852810       1 passthrough.go:48] ccResolverWrapper: sending update to cc: {[{https://127.0.0.1:2379  <nil> 0 <nil>}] <nil> <nil>}
I0903 11:02:42.852833       1 clientconn.go:948] ClientConn switching balancer to "pick_first"

例如，我希望找到與 etcd 和調度程序的通訊日誌。 api-server 和控制平面元件之間的通訊是否有任何日誌？