mirror of
https://github.com/optim-enterprises-bv/kubernetes.git
synced 2025-11-04 04:08:16 +00:00
84 lines
3.3 KiB
Markdown
84 lines
3.3 KiB
Markdown
<!-- BEGIN MUNGE: UNVERSIONED_WARNING -->
|
|
|
|
<!-- BEGIN STRIP_FOR_RELEASE -->
|
|
|
|
|
|
|
|
|
|
|
|
<h1>PLEASE NOTE: This document applies to the HEAD of the source
|
|
tree only. If you are using a released version of Kubernetes, you almost
|
|
certainly want the docs that go with that version.</h1>
|
|
|
|
<strong>Documentation for specific releases can be found at
|
|
[releases.k8s.io](http://releases.k8s.io).</strong>
|
|
|
|
|
|
|
|
|
|
|
|
<!-- END STRIP_FOR_RELEASE -->
|
|
|
|
<!-- END MUNGE: UNVERSIONED_WARNING -->
|
|
Running Multi-Node Kubernetes Using Docker
|
|
------------------------------------------
|
|
|
|
_Note_:
|
|
These instructions are somewhat significantly more advanced than the [single node](docker.md) instructions. If you are
|
|
interested in just starting to explore Kubernetes, we recommend that you start there.
|
|
|
|
_Note_:
|
|
There is a [bug](https://github.com/docker/docker/issues/14106) in Docker 1.7.0 that prevents this from working correctly.
|
|
Please install Docker 1.6.2 or wait for Docker 1.7.1.
|
|
|
|
**Table of Contents**
|
|
|
|
- [Prerequisites](#prerequisites)
|
|
- [Overview](#overview)
|
|
- [Bootstrap Docker](#bootstrap-docker)
|
|
- [Master Node](#master-node)
|
|
- [Adding a worker node](#adding-a-worker-node)
|
|
- [Testing your cluster](#testing-your-cluster)
|
|
|
|
## Prerequisites
|
|
1. You need a machine with docker installed.
|
|
|
|
## Overview
|
|
This guide will set up a 2-node kubernetes cluster, consisting of a _master_ node which hosts the API server and orchestrates work
|
|
and a _worker_ node which receives work from the master. You can repeat the process of adding worker nodes an arbitrary number of
|
|
times to create larger clusters.
|
|
|
|
Here's a diagram of what the final result will look like:
|
|
|
|
|
|
### Bootstrap Docker
|
|
This guide also uses a pattern of running two instances of the Docker daemon
|
|
1) A _bootstrap_ Docker instance which is used to start system daemons like ```flanneld``` and ```etcd```
|
|
2) A _main_ Docker instance which is used for the Kubernetes infrastructure and user's scheduled containers
|
|
|
|
This pattern is necessary because the ```flannel``` daemon is responsible for setting up and managing the network that interconnects
|
|
all of the Docker containers created by Kubernetes. To achieve this, it must run outside of the _main_ Docker daemon. However,
|
|
it is still useful to use containers for deployment and management, so we create a simpler _bootstrap_ daemon to achieve this.
|
|
|
|
## Master Node
|
|
The first step in the process is to initialize the master node.
|
|
|
|
See [here](docker-multinode/master.md) for detailed instructions.
|
|
|
|
## Adding a worker node
|
|
|
|
Once your master is up and running you can add one or more workers on different machines.
|
|
|
|
See [here](docker-multinode/worker.md) for detailed instructions.
|
|
|
|
## Testing your cluster
|
|
|
|
Once your cluster has been created you can [test it out](docker-multinode/testing.md)
|
|
|
|
For more complete applications, please look in the [examples directory](../../examples/)
|
|
|
|
|
|
<!-- BEGIN MUNGE: GENERATED_ANALYTICS -->
|
|
[]()
|
|
<!-- END MUNGE: GENERATED_ANALYTICS -->
|