feat: check kube-proxy and coredns in diagnose

kubeovn · Mar 12, 2020 · bdd021c · bdd021c
1 parent 5b64a25
commit bdd021c
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 0 deletions.
diff --git a/dist/images/install.sh b/dist/images/install.sh
@@ -796,6 +796,7 @@ for ns in $(kubectl get ns --no-headers -o  custom-columns=NAME:.metadata.name);
 done
 
 kubectl rollout status daemonset/kube-ovn-pinger -n kube-system
+kubectl rollout status deployment/coredns -n kube-system
 echo "-------------------------------"
 echo ""
 
@@ -933,10 +934,14 @@ vsctl(){
 diagnose(){
   kubectl get crd subnets.kubeovn.io
   kubectl get crd ips.kubeovn.io
+
+  checkDaemonSet kube-proxy
   checkDeployment ovn-central
   checkDeployment kube-ovn-controller
   checkDaemonSet kube-ovn-cni
   checkDaemonSet ovs-ovn
+  checkDeployment coredns
+
   type="$1"
   case $type in
     all)

diff --git a/dist/images/kubectl-ko b/dist/images/kubectl-ko
@@ -129,10 +129,13 @@ vsctl(){
 diagnose(){
   kubectl get crd subnets.kubeovn.io
   kubectl get crd ips.kubeovn.io
+
+  checkDaemonSet kube-proxy
   checkDeployment ovn-central
   checkDeployment kube-ovn-controller
   checkDaemonSet kube-ovn-cni
   checkDaemonSet ovs-ovn
+  checkDeployment coredns
   type="$1"
   case $type in
     all)