This is one of several issues which need to be overcome in order to remove Kubernetes from the base Atomic Host image.
This issue is a tracking issue for the various technical problems and bugs which prevent us from running the full Kubernetes infrastructure in containers. @jasonbrooks should have detail on what the specific blockers are.
I'm working on this, currently debugging some flannel system container issues.
My ansible scripts are here: https://github.com/jasonbrooks/contrib/tree/atomic-update.
I'm testing w/ two node, one master clusters based on a custom ostree tree built from: https://pagure.io/fork/jasonbrooks/fedora-atomic/branch/self-hosted-kube
RE the flannel issues I mentioned: https://github.com/projectatomic/atomic-system-containers/issues/28, fixed by https://github.com/projectatomic/atomic-system-containers/pull/29
What kind of container is targeted?
And is there a document describing the Kubernetes design on top of Atomic?
Regular docker containers for the kube components (https://github.com/jasonbrooks/k8s-images/tree/f25), and system containers for flannel and etcd (https://github.com/projectatomic/atomic-system-containers).
I'm not sure what you mean by kubernetes design on top of atomic.
We have working kubernetes system containers and working etcd and flannel system containers in fedora now.
moved to https://pagure.io/atomic/kubernetes-sig/issue/12
Metadata Update from @jasonbrooks:
- Issue close_status updated to: Duplicate
- Issue status updated to: Closed (was: Open)
to comment on this ticket.