Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RKT Pods for Kubelet + Wormhole Client #44

Closed
BugRoger opened this issue Sep 22, 2017 · 1 comment
Closed

RKT Pods for Kubelet + Wormhole Client #44

BugRoger opened this issue Sep 22, 2017 · 1 comment
Assignees

Comments

@BugRoger
Copy link
Contributor

Stick the kubelet and wormhole into the same rkt pod.

@SchwarzM
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants