jberkus added a new comment to an issue you are following: `` Well, OpenShift is its own thing rather than an alternative to Kubernetes. Some people want Kube, some want OpenShift.
So I've been doing a bunch with Kubeadm on AH. Jason's version does actually work, with some caveats:
1) it requires package layering, which really pushes up the idea of having a way for users to build their own OStree servers.
2) it doesn't work with setenforce=1. Even relabelling a bunch of directories, I have to setenforce 0 to get kubernetes to work reliably.
If we can get over those humps, though, I 'd like to push forward with something based on Kubeadm. I think it's the way the kubernetes project is headed, and it means that we can track them for anyone who wants to use kube-latest on Atomic. Importantly, the kubernetes community will continue to add features to kubeadm (like let's encrypt support), which won't happen with solutions we devise.
One of the things I was wondering about is maybe installing the kubeadm packages as part of Atomic. My reasoning is this: kubeadm is an installer rather than kubernetes itself. You can, in fact, use it to install an older/stable version of Kubernetes (back to 1.4.0, though), so we could track upstream Kubeadm without breaking people's stuff. Also, if not enabled in systemd (which it wouldn't be, by default), it doesn't interfere with installing something else like OpenShift.
``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/176