Cilium v1.5 Documentation44s Pod cilium-813gf is failing and has already been restarted 2 �mes. Let’s print the logfile of that pod to inves�gate the cause: $ kubectl --namespace kube-system logs cilium-813gf INFO and verify that each Cilium node is aware of the other nodes in the cluster. If not, check the logfile for errors. If nodes are being populated correctly, run tcpdump -n -i cilium_vxlan on each node0 码力 | 740 页 | 12.52 MB | 1 年前3- Cilium v1.6 Documentation44s Pod cilium-813gf is failing and has already been restarted 2 times. Let’s print the logfile of that pod to investigate the cause: $ kubectl --namespace kube-system logs cilium-813gf INFO and verify that each Cilium node is aware of the other nodes in the cluster. If not, check the logfile for errors. 4. If nodes are being populated correctly, run tcpdump -n -i cilium_vxlan on each node0 码力 | 734 页 | 11.45 MB | 1 年前3
- Cilium v1.7 Documentation44s Pod cilium-813gf is failing and has already been restarted 2 times. Let’s print the logfile of that pod to investigate the cause: $ kubectl --namespace kube-system logs cilium-813gf INFO and verify that each Cilium node is aware of the other nodes in the cluster. If not, check the logfile for errors. 4. If nodes are being populated correctly, run tcpdump -n -i cilium_vxlan on each node0 码力 | 885 页 | 12.41 MB | 1 年前3
- Cilium v1.8 Documentation44s Pod cilium-813gf is failing and has already been restarted 2 times. Let’s print the logfile of that pod to investigate the cause: $ kubectl --namespace kube-system logs cilium-813gf INFO and verify that each Cilium node is aware of the other nodes in the cluster. If not, check the logfile for errors. 4. If nodes are being populated correctly, run tcpdump -n -i cilium_vxlan on each node0 码力 | 1124 页 | 21.33 MB | 1 年前3
- Cilium v1.10 Documentation44s Pod cilium-813gf is failing and has already been restarted 2 times. Let’s print the logfile of that pod to investigate the cause: $ kubectl --namespace kube-system logs cilium-813gf INFO and verify that each Cilium node is aware of the other nodes in the cluster. If not, check the logfile for errors. 4. If nodes are being populated correctly, run tcpdump -n -i cilium_vxlan on each node0 码力 | 1307 页 | 19.26 MB | 1 年前3
- Cilium v1.9 Documentation44s Pod cilium-813gf is failing and has already been restarted 2 times. Let’s print the logfile of that pod to investigate the cause: $ kubectl --namespace kube-system logs cilium-813gf INFO and verify that each Cilium node is aware of the other nodes in the cluster. If not, check the logfile for errors. 4. If nodes are being populated correctly, run tcpdump -n -i cilium_vxlan on each node0 码力 | 1263 页 | 18.62 MB | 1 年前3
- Cilium v1.11 Documentation44s Pod cilium-813gf is failing and has already been restarted 2 times. Let’s print the logfile of that pod to investigate the cause: $ kubectl --namespace kube-system logs cilium-813gf INFO and verify that each Cilium node is aware of the other nodes in the cluster. If not, check the logfile for errors. 4. If nodes are being populated correctly, run tcpdump -n -i cilium_vxlan on each node0 码力 | 1373 页 | 19.37 MB | 1 年前3
共 7 条
- 1