Fix for containerd restart issue while deploying the Mizar YAML

CentaurusInfra / mizar

Mizar – Experimental, High Scale and High Performance Cloud Network https://mizar.readthedocs.io

https://mizar.readthedocs.io

GNU General Public License v2.0

111 stars 50 forks source link

Closed click2cloud-team1 closed 3 years ago

click2cloud-team1 commented 3 years ago

This PR fixes the containerd restart issue after applying the Mizar single deployment YAML.
The conf file should be a regular file and it should be generated after the binary is placed in the respective location.
We have tested using the modified image of mizar container (c2cengg20190034/mizar:0.9) on OnPrem as well as GCE.

vinaykul commented 3 years ago

I assume that you have tested it in GCE via kube-up. Has this change also been tested for upstream k8s as well? Does this also work with arktos-up?

click2cloud-team1 commented 3 years ago

I assume that you have tested it in GCE via kube-up. Has this change also been tested for upstream k8s as well? Does this also work with arktos-up?

Yes, we tested this via kube-up, arktos-up and in upstream k8s (kubeadm)