You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sadly the information for coreos pods is scarce but I managed to find some and try it out.
It seems that what we want to achieve (tying kubelet and wormhole together) is not easily achieved.
According to the architecture docs.
A normal pod is without supervision meaning if one container dies the other one is happily running and continues to do so. Unless there is some way of supervision no one takes care about the state of the apps deployed.
Using systemd / nspawn supervision inside the pod is artificial as it could also be done with systemd outside the pod as well.
While I like the idea of using a json to define the pod, volumes and ports in a kubernetes style way I think currently it makes no sense in this case.
Stick the
kubelet
andwormhole
into the same rkt pod.The text was updated successfully, but these errors were encountered: