Mizar daemon and operator should be under kube-system namespace instead of the default ns

[yb01]

Minor issue. can be post 130.

What happened:

the mizar daemon and operator should be under kube-system namespace instead of the default ns.

root@ip-172-31-39-83:~/go/src/k8s.io/arktos# kubectl get pods -AT -o wide
TENANT   NAMESPACE     NAME                               HASHKEY               READY   STATUS             RESTARTS   AGE    IP             NODE              NOMINATED NODE   READINESS GATES
system   default       mizar-daemon-vpbrt                 6002164738579425396   1/1     Running            0          106m   172.31.39.83   ip-172-31-39-83   <none>           <none>
system   default       mizar-operator-5c97f7478d-j7qps    9068998367428645618   1/1     Running            0          106m   172.31.39.83   ip-172-31-39-83   <none>           <none>

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Mizar version:
• Cloud provider or hardware configuration:
• OS (e.g: cat /etc/os-release):
• Kernel (e.g. uname -a):
• Install tools:
• Network plugin and version (if this is a network-related bug):
• Others:

[vinaykul]

I agree but this may not be a trivial fix. We will take this up post-release.