From 7ee4cfe54c37e544e0ba15633f3f8a34ae1d4917 Mon Sep 17 00:00:00 2001 From: Avesh Agarwal Date: Thu, 19 Mar 2015 07:19:16 -0400 Subject: [PATCH] Fixes to Kubernetes/Fedora upstream guide. --- .../fedora/fedora_manual_config.md | 66 ++++++++++++------- 1 file changed, 41 insertions(+), 25 deletions(-) diff --git a/docs/getting-started-guides/fedora/fedora_manual_config.md b/docs/getting-started-guides/fedora/fedora_manual_config.md index 6dca248fb4d..49869f2e55a 100644 --- a/docs/getting-started-guides/fedora/fedora_manual_config.md +++ b/docs/getting-started-guides/fedora/fedora_manual_config.md @@ -2,9 +2,9 @@ This is a getting started guide for Fedora. It is a manual configuration so you understand all the underlying packages / services / ports, etc... -This guide will only get ONE minion working. Multiple minions requires a functional [networking configuration](https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/networking.md) done outside of kubernetes. Although the additional kubernetes configuration requirements should be obvious. +This guide will only get ONE minion working. Multiple minions require a functional [networking configuration](https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/networking.md) done outside of kubernetes. Although the additional kubernetes configuration requirements should be obvious. -The kubernetes package provides a few services: kube-apiserver, kube-scheduler, kube-controller-manager, kubelet, kube-proxy. These services are managed by systemd and the configuration resides in a central location: /etc/kubernetes. We will break the services up between the hosts. The first host, fed-master, will be the kubernetes master. This host will run the kube-apiserver, kube-controller-manager, and kube-scheduler. In addition, the master will also run _etcd_. The remaining host, fed-minion will be the minion and run kubelet, proxy, cadvisor and docker. +The kubernetes package provides a few services: kube-apiserver, kube-scheduler, kube-controller-manager, kubelet, kube-proxy. These services are managed by systemd and the configuration resides in a central location: /etc/kubernetes. We will break the services up between the hosts. The first host, fed-master, will be the kubernetes master. This host will run the kube-apiserver, kube-controller-manager, and kube-scheduler. In addition, the master will also run _etcd_ (not needed if _etcd_ runs on a different host but this guide assumes that _etcd_ and kubernetes master run on the same host). The remaining host, fed-minion will be the minion and run kubelet, proxy and docker. **System Information:** @@ -16,13 +16,13 @@ fed-minion = 192.168.121.65 **Prepare the hosts:** -* Install kubernetes on all hosts - fed-{master,minion}. This will also pull in etcd, docker, and cadvisor. +* Install kubernetes on all hosts - fed-{master,minion}. This will also pull in etcd and docker. This guide has been tested with kubernetes-0.12.0 but should work with later versions too. ``` yum -y install --enablerepo=updates-testing kubernetes ``` -* Add master and minion to /etc/hosts on all machines (not needed if hostnames already in DNS) +* Add master and minion to /etc/hosts on all machines (not needed if hostnames already in DNS). Make sure that communication works between fed-master and fed-minion by using a utility such as ping. ``` echo "192.168.121.9 fed-master @@ -33,7 +33,7 @@ echo "192.168.121.9 fed-master ``` # Comma separated list of nodes in the etcd cluster -KUBE_ETCD_SERVERS="--etcd_servers=http://fed-master:4001" +KUBE_MASTER="--master=http://fed-master:8080" # logging to stderr means we get it in the systemd journal KUBE_LOGTOSTDERR="--logtostderr=true" @@ -45,7 +45,7 @@ KUBE_LOG_LEVEL="--v=0" KUBE_ALLOW_PRIV="--allow_privileged=false" ``` -* Disable the firewall on both the master and minon, as docker does not play well with other firewall rule managers +* Disable the firewall on both the master and minion, as docker does not play well with other firewall rule managers. Please note that iptables-services does not exist on default fedora server install. ``` systemctl disable iptables-services firewalld @@ -54,20 +54,14 @@ systemctl stop iptables-services firewalld **Configure the kubernetes services on the master.** -* Edit /etc/kubernetes/apiserver to appear as such: +* Edit /etc/kubernetes/apiserver to appear as such. The portal_net IP addresses must be an unused block of addresses, not used anywhere else. They do not need to be routed or assigned to anything. -``` +``` # The address on the local server to listen to. KUBE_API_ADDRESS="--address=0.0.0.0" -# The port on the local server to listen on. -KUBE_API_PORT="--port=8080" - -# How the replication controller and scheduler find the kube-apiserver -KUBE_MASTER="--master=http://fed-master:8080" - -# Port minions listen on -KUBELET_PORT="--kubelet_port=10250" +# Comma separated list of nodes in the etcd cluster +KUBE_ETCD_SERVERS="--etcd_servers=http://fed-master:4001" # Address range to use for services KUBE_SERVICE_ADDRESSES="--portal_net=10.254.0.0/16" @@ -78,8 +72,15 @@ KUBE_API_ARGS="" * Edit /etc/kubernetes/controller-manager to appear as such: ``` +# The following values are used to configure the kubernetes controller-manager + +# defaults from config and apiserver should be adequate + # Comma separated list of minions KUBELET_ADDRESSES="--machines=fed-minion" + +# Add you own! +KUBE_CONTROLLER_MANAGER_ARGS="" ``` * Start the appropriate services on master: @@ -94,23 +95,38 @@ done **Configure the kubernetes services on the minion.** -***We need to configure the kubelet and start the kubelet and proxy*** +***We need to configure the kubelet and proxy and start them.*** * Edit /etc/kubernetes/kubelet to appear as such: -``` -# The address for the info server to serve on -KUBELET_ADDRESS="--address=0.0.0.0" +``` +### +# kubernetes kubelet (minion) config -# The port for the info server to serve on -KUBELET_PORT="--port=10250" +# 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=fed-minion" +# location of the api-server +KUBELET_API_SERVER="--api_servers=http://fed-master:8080" + # Add your own! -KUBELET_ARGS="" -``` +#KUBELET_ARGS="" +``` + +* Edit /etc/kubernetes/proxy to appear as such: + +``` +### +# kubernetes proxy config + +# default config should be adequate + +# Add your own! +KUBE_PROXY_ARGS="--master=http://fed-master:8080" +``` * Start the appropriate services on minion (fed-minion). @@ -124,7 +140,7 @@ done *You should be finished!* -* Check to make sure the cluster can see the minion (on fed-master) +* Check to make sure the cluster can see the minion (on fed-master). ``` kubectl get minions