Showing posts with label Continuous Integration. Show all posts
Showing posts with label Continuous Integration. Show all posts

Sunday, April 5, 2015

The Cloudcast #185 - Masters, Minions and Pods - Kubernetes 101

Topic 1 - Let’s talk a little bit about your background and why we asked you to come discuss Kubernetes tonight.

Topic 2 - We’re all familiar with Docker at this point, and generally familiar with the underlying container technologies. So where does Kubernetes fit in? (who runs it? what’s the input to the scheduler? what does it use to track resources at the host level? does it assume all machines are the same?)

Topic 2a - What makes Kubernetes easy to use and hard to use?

Topic 2b - Does it use/assume all the native container management tools, or does Kubernetes do some of that tool?

Topic 3 - Let’s walk through the basic concepts and suggested best practices around things like #apps/container, tagging and pods.
Topic 4 - Since Kubernetes came from Google, every just assumes it deals with scale well. But how does the scaling of that control plane work? Is it a single data-center view, multi-data center or smaller segments within a data-center?

Topic 5 - What Google-specific assumptions are built into Kubernetes that might not be broadly applicable to other companies?

Topic 6 - What are some of the common applications that companies use to get started with Kubernetes?

Wednesday, October 29, 2014

The Cloudcast #168 - Containerized Continuous Delivery

Topic 1 - You have an very interesting background to some of our listeners having been involved in XBox Live and Kinect platforms. What was that like? What CI/CD needs to you encounter?

Topic 2 - CI/CD with a “developer cloud” focus. Where does Jenkins fit into this picture? Is Jenkins more about vm’s and this is about containers? You mentioned in an interview that code and apps are in the cloud (github) but CI is in-house, that didn’t make sense to you.

Follow Up: As I see it, a developer can spin up a container on their laptop, then move this container to another environment test/det, AWS, production in house, etc. and you are potentially removing the gotchas of “It worked on my laptop”, correct?

Topic 3 - In addition, what other problems you are trying to solve with Containerized CI/CD? Faster time to value? Portability between environments? All of the above? I see you have integration with Docker Hub, Chef, Puppet, even Kubernetes

Topic 4 - We keep mentioning micro-service as an architecture on the show. Is this an example of the CI/CD ecosystem evolving to embrace containers and a micro-service architecture?

Topic 5 - You also did a podcast with friend of the show Lucas Carlson ( We had him on to discuss Panamax. Do you integrate with Panamax?