Documentation

Resilience-Controller

  1. Run the following command to check the pod of the Resilience-Controller in the Kubernetes cluster. Ensure that STATUS of the pod is Running and READY is 1/1.
    kubectl get pods -n mindx-dl -o wide

    Information similar to the following is displayed.

    root@ubuntu:/usr/local/bin# kubectl get pods -n mindx-dl -o wide
NAME                                           READY   STATUS    RESTARTS   AGE     IP               NODE         NOMINATED NODE   READINESS GATES
resilience-controller-76f4476bb5-fs986         1/1     Running   0          6m52s   192.168.102.67   ubuntu       <none>           <none>
...
  2. Run the following command to view Resilience-Controller logs in the Kubernetes cluster:
    kubectl logs -n mindx-dl {name_of_the_Resilience's pod}

    If the following information is displayed, the component is normal:

    root@ubuntu:~# kubectl logs -n mindx-dl resilience-controller-76f4476bb5-fs986 
[INFO]     2022/11/17 17:18:46.697010 1       hwlog@v0.0.0/api.go:96    run.log's logger init success
[INFO]     2022/11/17 17:18:46.697139 1       cmd/main.go:57    resilience-controller starting and the version is v3.0.0_linux-x86_64
[INFO]     2022/11/17 17:18:47.227913 1       K8stool@v0.0.0/self_K8s_client.go:116    start to decrypt cfg
[INFO]     2022/11/17 17:18:47.297559 1       K8stool@v0.0.0/self_K8s_client.go:125    Config loaded from file: ****tc/mindx-dl/resilience-controller/.config/config6
[INFO]     2022/11/17 17:18:47.300066 1       elastic/controller.go:45    Setting up elastic event handlers
[INFO]     2022/11/17 17:18:47.300179 1       elastic/controller.go:63    Starting elastic controller, waiting for informer caches to sync
[INFO]     2022/11/17 17:18:47.401246 1       cmd/main.go:80    elastic controller started
...