Organization of pods in cluster in Google Container Engine

What is the usual way to organize pods in a cluster in Kubernetes?

I have a Jenkins build server, Docker registry, Git repository and other development tools that I want to run in Google Container Engine. Do I create one cluster for each of them? Or can multiple pods be scheduled on each node?

  • Unable to connect to SQL Server Express container on host VM
  • UDP packets aren't forwarded to Node Application inside of docker container
  • Disk management (cleanup) in a stopped docker container
  • docker-compose - unable to attach to containers
  • Docker containers cannot connect through overlay networks
  • Unable To Disconnect Docker Container From Network
  • So my question is: Would you create one cluster that holds all these services, or multiple clusters?
    The same question applies to production, qa etc enviroments. Do I create one cluster for each enviroment or do I have them in the same cluster?

  • Stop Solr gracefully when it running in docker
  • How to apply new logrotate config for syslog, without restarting the system?
  • How to “add” the proxy section to configure a registry as a pull-through cache?
  • How to prevent RabbitMQ settings to be lost during intermediate steps of a Dockerfile?
  • docker 1.9 registry API change
  • Docker Best Practises: at what size application should you refrain from containerising?
  • One Solution collect form web for “Organization of pods in cluster in Google Container Engine”

    To answer your first question, multiple pods can be scheduled on each node.

    One of the best parts about Google Container Engine / Kubernetes is that it is really flexible, so you can structure your services in the way that works best for you. For your specific use case, I think that a single cluster would make sense because all of the applications that you want to run are closely related. You’ll want to think a bit about choosing an appropriate size for your cluster (both the number of VMs and the size of each VM) to fit your entire workload.

    You can experiment with creating a single cluster for both your QA and Prod workloads, or you can split them across clusters. Until Kubernetes has better support for QoS (for scheduling pods), it probably makes more sense to keep the QA environment separate (and probably sized more modestly).

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.