Skip to content

post about atomic system containers and kubernetes - #353

Closed
jasonbrooks wants to merge 2 commits into
projectatomic:masterfrom
jasonbrooks:pr-system-containers-kube
Closed

post about atomic system containers and kubernetes#353
jasonbrooks wants to merge 2 commits into
projectatomic:masterfrom
jasonbrooks:pr-system-containers-kube

Conversation

@jasonbrooks

Copy link
Copy Markdown
Contributor

No description provided.

@jberkus

jberkus commented Aug 19, 2016

Copy link
Copy Markdown
Contributor

@bproffitt I'd like to push this monday but see discussion below.

@cgwalters

Copy link
Copy Markdown
Member

Can we hold on this a bit and collaborate more on CentOS/sig-atomic-buildscripts#144 ?

@jberkus

jberkus commented Aug 19, 2016

Copy link
Copy Markdown
Contributor

@cgwalters why? This post gives something people can do right now. I can see referencing the ongoing work in the post, though ...

@jlebon

jlebon commented Aug 22, 2016

Copy link
Copy Markdown
Contributor

@jberkus Because it's part of a larger story with a better hook. The idea here is that we're trimming the host and migrating to containers. We haven't done the trimming yet (this is what CentOS/sig-atomic-buildscripts#144 does) and the final architecture is still being decided & tested. I'd also be in favour of waiting for that to happen and then rewriting this a bit to get a more compelling story.

@cgwalters

Copy link
Copy Markdown
Member

@jasonbrooks

Copy link
Copy Markdown
Contributor Author

This post isn't meant to be about what centos is doing with its alpha branch, it's meant to be about how you can run kube 1.3 on atomic, even though we have no kube 1.3 rpms, and about how to run flannel and etcd in system containers, because that's an interesting new feature that's not really documented yet.

I put it on my personal blog originally because it includes lots of unofficial things, the flannel and etcd containers from Giuseppe and the kube container straight from upstream, and the continuous branch required for the right atomic command version. I can see an argument for putting more fully-baked things on the project atomic blog, and I can see the argument for putting more in-development things on here.

For instance, we're asking people to +1 the flannel/etcd in system containers idea, but people have had little opportunity to check this out / learn about it to inform their feedback. A post like this gives you a working current kube setup based on these pieces.

Either way, I'm happy to write about the reorganized centos atomic host when it's ready.

@jberkus

jberkus commented Aug 22, 2016

Copy link
Copy Markdown
Contributor

@jlebon, @cgwalters :

We support the kubernetes project. LDK is our stack. We present stuff at, and sometimes run, Kubernetes meetups. Kubernetes 1.3 has been out for more than a month. While our users want to know our roapmap for containerizing all of the services, they also want to be able to run 1.3 on atomic now.

So while I think adding a link to the ongoing work makes sense, I disagree that we should wait and not post this because we want to hold off until the system containers are done. This is an OSS project, we should be encouraging people to hack it.

@cgwalters

Copy link
Copy Markdown
Member

So now that the CAHC Alpha is out, I think this is also good but would like to see a reference to that as well.

@jberkus

jberkus commented Aug 31, 2016

Copy link
Copy Markdown
Contributor

@jasonbrooks do you want to update the post to reference the other one, or do you want me to do it?

@jasonbrooks

Copy link
Copy Markdown
Contributor Author

@jberkus I'll update it tomorrow


# atomic pull gscrivano/flannel

# atomic install --system gscrivano/etcd

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Needs systemctl start etcd after this.

@jlebon

jlebon commented Sep 8, 2016

Copy link
Copy Markdown
Contributor

This is pretty cool! I made some comments which are mostly to update it to the latest way of doing things in atomic.

@jberkus

jberkus commented Sep 14, 2016

Copy link
Copy Markdown
Contributor

Looks good. Barring some kind of objection, I'll push this tommorrow.

@jberkus

jberkus commented Sep 15, 2016

Copy link
Copy Markdown
Contributor

Replaced with PR #363 so I could change the date. Merging that one.

@jberkus jberkus closed this Sep 15, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants