forked from kubernetes/kubernetes
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request kubernetes#12887 from djosborne/master
added calico-kubernetes-fedora-digitalocean demo
- Loading branch information
Showing
2 changed files
with
353 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,352 @@ | ||
<!-- BEGIN MUNGE: UNVERSIONED_WARNING --> | ||
|
||
<!-- BEGIN STRIP_FOR_RELEASE --> | ||
|
||
<img src="http://kubernetes.io/img/warning.png" alt="WARNING" | ||
width="25" height="25"> | ||
<img src="http://kubernetes.io/img/warning.png" alt="WARNING" | ||
width="25" height="25"> | ||
<img src="http://kubernetes.io/img/warning.png" alt="WARNING" | ||
width="25" height="25"> | ||
<img src="http://kubernetes.io/img/warning.png" alt="WARNING" | ||
width="25" height="25"> | ||
<img src="http://kubernetes.io/img/warning.png" alt="WARNING" | ||
width="25" height="25"> | ||
|
||
<h2>PLEASE NOTE: This document applies to the HEAD of the source tree</h2> | ||
|
||
If you are using a released version of Kubernetes, you should | ||
refer to the docs that go with that version. | ||
|
||
<strong> | ||
The latest 1.0.x release of this document can be found | ||
[here](http://releases.k8s.io/release-1.0/docs/getting-started-guides/fedora/fedora-calico.md). | ||
|
||
Documentation for other releases can be found at | ||
[releases.k8s.io](http://releases.k8s.io). | ||
</strong> | ||
-- | ||
|
||
<!-- END STRIP_FOR_RELEASE --> | ||
|
||
<!-- END MUNGE: UNVERSIONED_WARNING --> | ||
|
||
Running Kubernetes with [Calico Networking](http://projectcalico.org) on a [Digital Ocean](http://digitalocean.com) [Fedora Host](http://fedoraproject.org) | ||
----------------------------------------------------- | ||
|
||
## Table of Contents | ||
|
||
* [Prerequisites](#prerequisites) | ||
* [Overview](#overview) | ||
* [Setup Communication Between Hosts](#setup-communication-between-hosts) | ||
* [Setup Master](#setup-master) | ||
* [Install etcd](#install-etcd) | ||
* [Install Kubernetes](#install-kubernetes) | ||
* [Install Calico](#install-calico) | ||
* [Setup Node](#setup-node) | ||
* [Configure the Virtual Interface - cbr0](#configure-the-virtual-interface---cbr0) | ||
* [Install Docker](#install-docker) | ||
* [Install Calico](#install-calico-1) | ||
* [Install Kubernetes](#install-kubernetes-1) | ||
* [Check Running Cluster](#check-running-cluster) | ||
|
||
## Prerequisites | ||
|
||
You need two or more Fedora 22 droplets on Digital Ocean with [Private Networking](https://www.digitalocean.com/community/tutorials/how-to-set-up-and-use-digitalocean-private-networking) enabled. | ||
|
||
## Overview | ||
|
||
This guide will walk you through the process of getting a Kubernetes Fedora cluster running on Digital Ocean with networking powered by Calico networking. It will cover the installation and configuration of the following systemd processes on the following hosts: | ||
|
||
Kubernetes Master: | ||
- `kube-apiserver` | ||
- `kube-controller-manager` | ||
- `kube-scheduler` | ||
- `etcd` | ||
- `docker` | ||
- `calico-node` | ||
|
||
Kubernetes Node: | ||
- `kubelet` | ||
- `kube-proxy` | ||
- `docker` | ||
- `calico-node` | ||
|
||
For this demo, we will be setting up one Master and one Node with the following information: | ||
|
||
| Hostname | IP | | ||
|-------------|-------------| | ||
| kube-master |10.134.251.56| | ||
| kube-node-1 |10.134.251.55| | ||
|
||
This guide is scalable to multiple nodes provided you [configure interface-cbr0 with its own subnet on each Node](#configure-the-virtual-interface---cbr0) and [add an entry to /etc/hosts for each host](#setup-communication-between-hosts). | ||
|
||
Ensure you substitute the IP Addresses and Hostnames used in this guide with ones in your own setup. | ||
|
||
## Setup Communication Between Hosts | ||
|
||
Digital Ocean private networking configures a private network on eth1 for each host. To simplify communication between the hosts, we will add an entry to /etc/hosts so that all hosts in the cluster can hostname-resolve one another to this interface. **It is important that the hostname resolves to this interface instead of eth0, as all Kubernetes and Calico services will be running on it.** | ||
|
||
``` | ||
echo "10.134.251.56 kube-master" >> /etc/hosts | ||
echo "10.134.251.55 kube-node-1" >> /etc/hosts | ||
``` | ||
|
||
>Make sure that communication works between kube-master and each kube-node by using a utility such as ping. | ||
## Setup Master | ||
|
||
### Install etcd | ||
|
||
* Both Calico and Kubernetes use etcd as their datastore. We will run etcd on Master and point all Kubernetes and Calico services at it. | ||
|
||
``` | ||
yum -y install etcd | ||
``` | ||
|
||
* Edit `/etc/etcd/etcd.conf` | ||
|
||
``` | ||
ETCD_LISTEN_CLIENT_URLS="http://kube-master:4001" | ||
ETCD_ADVERTISE_CLIENT_URLS="http://kube-master:4001" | ||
``` | ||
|
||
### Install Kubernetes | ||
|
||
* Run the following command on Master to install the latest Kubernetes (as well as docker): | ||
|
||
``` | ||
yum -y install kubernetes | ||
``` | ||
|
||
* Edit `/etc/kubernetes/config ` | ||
|
||
``` | ||
# How the controller-manager, scheduler, and proxy find the apiserver | ||
KUBE_MASTER="--master=http://kube-master:8080" | ||
``` | ||
|
||
* Edit `/etc/kubernetes/apiserver` | ||
|
||
``` | ||
# The address on the local server to listen to. | ||
KUBE_API_ADDRESS="--insecure-bind-address=0.0.0.0" | ||
KUBE_ETCD_SERVERS="--etcd-servers=http://kube-master:4001" | ||
# Remove ServiceAccount from this line to run without API Tokens | ||
KUBE_ADMISSION_CONTROL="--admission-control=NamespaceLifecycle,NamespaceExists,LimitRanger,SecurityContextDeny,ResourceQuota" | ||
``` | ||
|
||
* Create /var/run/kubernetes on master: | ||
|
||
``` | ||
mkdir /var/run/kubernetes | ||
chown kube:kube /var/run/kubernetes | ||
chmod 750 /var/run/kubernetes | ||
``` | ||
|
||
* Start the appropriate services on master: | ||
|
||
``` | ||
for SERVICE in etcd kube-apiserver kube-controller-manager kube-scheduler; do | ||
systemctl restart $SERVICE | ||
systemctl enable $SERVICE | ||
systemctl status $SERVICE | ||
done | ||
``` | ||
|
||
### Install Calico | ||
|
||
Next, we'll launch Calico on Master to allow communication between Pods and any services running on the Master. | ||
* Install calicoctl, the calico configuration tool. | ||
|
||
``` | ||
wget https://github.com/Metaswitch/calico-docker/releases/download/v0.5.5/calicoctl | ||
chmod +x ./calicoctl | ||
sudo mv ./calicoctl /usr/bin | ||
``` | ||
|
||
* Create `/etc/systemd/system/calico-node.service` | ||
|
||
``` | ||
[Unit] | ||
Description=calicoctl node | ||
Requires=docker.service | ||
After=docker.service | ||
[Service] | ||
User=root | ||
Environment="ETCD_AUTHORITY=kube-master:4001" | ||
PermissionsStartOnly=true | ||
ExecStartPre=/usr/bin/calicoctl checksystem --fix | ||
ExecStart=/usr/bin/calicoctl node --ip=10.134.251.56 --detach=false | ||
[Install] | ||
WantedBy=multi-user.target | ||
``` | ||
|
||
>Be sure to substitute `--ip=10.134.251.56` with your Master's eth1 IP Address. | ||
* Start Calico | ||
|
||
``` | ||
systemctl enable calico-node.service | ||
systemctl start calico-node.service | ||
``` | ||
|
||
>Starting calico for the first time may take a few minutes as the calico-node docker image is downloaded. | ||
## Setup Node | ||
|
||
### Configure the Virtual Interface - cbr0 | ||
|
||
By default, docker will create and run on a virtual interface called `docker0`. This interface is automatically assigned the address range 172.17.42.1/16. In order to set our own address range, we will create a new virtual interface called `cbr0` and then start docker on it. | ||
|
||
* Add a virtual interface by creating `/etc/sysconfig/network-scripts/ifcfg-cbr0`: | ||
|
||
``` | ||
DEVICE=cbr0 | ||
TYPE=Bridge | ||
IPADDR=192.168.1.1 | ||
NETMASK=255.255.255.0 | ||
ONBOOT=yes | ||
BOOTPROTO=static | ||
``` | ||
|
||
>**Note for Multi-Node Clusters:** Each node should be assigned an IP address on a unique subnet. In this example, node-1 is using 192.168.1.1/24, so node-2 should be assigned another pool on the 192.168.x.0/24 subnet, e.g. 192.168.2.1/24. | ||
* Ensure that your system has bridge-utils installed. Then, restart the networking daemon to activate the new interface | ||
|
||
``` | ||
systemctl restart network.service | ||
``` | ||
|
||
### Install Docker | ||
|
||
* Install Docker | ||
|
||
``` | ||
yum -y install docker | ||
``` | ||
|
||
* Configure docker to run on `cbr0` by editing `/etc/sysconfig/docker-network`: | ||
|
||
``` | ||
DOCKER_NETWORK_OPTIONS="--bridge=cbr0 --iptables=false --ip-masq=false" | ||
``` | ||
|
||
* Start docker | ||
|
||
``` | ||
systemctl start docker | ||
``` | ||
|
||
### Install Calico | ||
|
||
* Install calicoctl, the calico configuration tool. | ||
|
||
``` | ||
wget https://github.com/Metaswitch/calico-docker/releases/download/v0.5.5/calicoctl | ||
chmod +x ./calicoctl | ||
sudo mv ./calicoctl /usr/bin | ||
``` | ||
|
||
* Create `/etc/systemd/system/calico-node.service` | ||
|
||
``` | ||
[Unit] | ||
Description=calicoctl node | ||
Requires=docker.service | ||
After=docker.service | ||
[Service] | ||
User=root | ||
Environment="ETCD_AUTHORITY=kube-master:4001" | ||
PermissionsStartOnly=true | ||
ExecStartPre=/usr/bin/calicoctl checksystem --fix | ||
ExecStart=/usr/bin/calicoctl node --ip=10.134.251.55 --detach=false --kubernetes | ||
[Install] | ||
WantedBy=multi-user.target | ||
``` | ||
|
||
> Note: You must replace the IP address with your node's eth1 IP Address! | ||
* Start Calico | ||
|
||
``` | ||
systemctl enable calico-node.service | ||
systemctl start calico-node.service | ||
``` | ||
|
||
* Configure the IP Address Pool | ||
|
||
Most Kubernetes application deployments will require communication between Pods and the kube-apiserver on Master. On a standard Digital Ocean Private Network, requests sent from Pods to the kube-apiserver will not be returned as the networking fabric will drop response packets destined for any 192.168.0.0/16 address. To resolve this, you can have calicoctl add a masquerade rule to all outgoing traffic on the node: | ||
|
||
``` | ||
ETCD_AUTHORITY=kube-master:4001 calicoctl pool add 192.168.0.0/16 --nat-outgoing | ||
``` | ||
|
||
### Install Kubernetes | ||
|
||
* First, install Kubernetes. | ||
|
||
``` | ||
yum -y install kubernetes | ||
``` | ||
|
||
* Edit `/etc/kubernetes/config` | ||
|
||
``` | ||
# How the controller-manager, scheduler, and proxy find the apiserver | ||
KUBE_MASTER="--master=http://kube-master:8080" | ||
``` | ||
|
||
* Edit `/etc/kubernetes/kubelet` | ||
|
||
We'll pass in an extra parameter - `--network-plugin=calico` to tell the Kubelet to use the Calico networking plugin. Additionally, we'll add two environment variables that will be used by the Calico networking plugin. | ||
|
||
``` | ||
# The address for the info server to serve on (set to 0.0.0.0 or "" for all interfaces) | ||
KUBELET_ADDRESS="--address=0.0.0.0" | ||
# You may leave this blank to use the actual hostname | ||
# KUBELET_HOSTNAME="--hostname-override=127.0.0.1" | ||
# location of the api-server | ||
KUBELET_API_SERVER="--api-servers=http://kube-master:8080" | ||
# Add your own! | ||
KUBELET_ARGS="--network-plugin=calico" | ||
# The following are variables which the kubelet will pass to the calico-networking plugin | ||
ETCD_AUTHORITY="kube-master:4001" | ||
KUBE_API_ROOT="http://kube-master:8080/api/v1" | ||
``` | ||
|
||
* Start Kubernetes on the node. | ||
|
||
``` | ||
for SERVICE in kube-proxy kubelet; do | ||
systemctl restart $SERVICE | ||
systemctl enable $SERVICE | ||
systemctl status $SERVICE | ||
done | ||
``` | ||
|
||
## Check Running Cluster | ||
|
||
The cluster should be running! Check that your nodes are reporting as such: | ||
|
||
``` | ||
kubectl get nodes | ||
NAME LABELS STATUS | ||
kube-node-1 kubernetes.io/hostname=kube-node-1 Ready | ||
``` | ||
|
||
|
||
<!-- BEGIN MUNGE: GENERATED_ANALYTICS --> | ||
[![Analytics](https://kubernetes-site.appspot.com/UA-36037335-10/GitHub/docs/getting-started-guides/fedora/fedora-calico.md?pixel)]() | ||
<!-- END MUNGE: GENERATED_ANALYTICS --> |