Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fedora guide updates #2873

Merged
merged 3 commits into from
Dec 12, 2014
Merged

Fedora guide updates #2873

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
820ce26
make kubelet listen on 0.0.0.0 in the fedora guide
eparis Dec 11, 2014
c489c30
Stop telling people how to launch a pod. That's what 101 is for.
eparis Dec 11, 2014
47177c9
Remove a bunch of boilerplate and testing/poking as you go
eparis Dec 11, 2014
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
181 changes: 4 additions & 177 deletions docs/getting-started-guides/fedora/fedora_manual_config.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,12 +4,6 @@ This is a getting started guide for Fedora. It is a manual configuration so you

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.

The guide is broken into 3 sections:

1. Prepare the hosts.
2. Configuring the two hosts, a master and a minion.
3. Basic functionality test.

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.

**System Information:**
Expand All @@ -20,16 +14,6 @@ fed-master = 192.168.121.9
fed-minion = 192.168.121.65
```

Versions:

```
Fedora release 20 (Heisenbug)

etcd-0.4.6-6.fc20.x86_64
kubernetes-0.4-0.2.gitd5377e4.fc22.x86_64
```


**Prepare the hosts:**

* Install kubernetes on all hosts - fed-{master,minion}. This will also pull in etcd, docker, and cadvisor.
Expand All @@ -45,21 +29,9 @@ echo "192.168.121.9 fed-master
192.168.121.65 fed-minion" >> /etc/hosts
```

* Edit /etc/kubernetes/config which will be the same on all hosts
* Edit /etc/kubernetes/config which will be the same on all hosts to contain:

```
###
# kubernetes system config
#
# The following values are used to configure various aspects of all
# kubernetes services, including
#
# kube-apiserver.service
# kube-controller-manager.service
# kube-scheduler.service
# kubelet.service
# kube-proxy.service

# Comma seperated list of nodes in the etcd cluster
KUBE_ETCD_SERVERS="--etcd_servers=http://fed-master:4001"

Expand All @@ -82,17 +54,9 @@ systemctl stop iptables-services firewalld

**Configure the kubernetes services on the master.**

***For this you need to configure the kube-apiserver. The kube-apiserver, kube-controller-manager, and kube-scheduler along with the etcd, will need to be started***

* Edit /etc/kubernetes/apiserver to appear as such:

```
###
# kubernetes system config
#
# The following values are used to configure the kube-apiserver
#

# The address on the local server to listen to.
KUBE_API_ADDRESS="--address=0.0.0.0"

Expand All @@ -114,12 +78,6 @@ KUBE_API_ARGS=""

* Edit /etc/kubernetes/controller-manager to appear as such:
```
###
# kubernetes system config
#
# The following values are used to configure the kube-controller-manager
#

# Comma seperated list of minions
KUBELET_ADDRESSES="--machines=fed-minion"
```
Expand All @@ -134,40 +92,15 @@ for SERVICES in etcd kube-apiserver kube-controller-manager kube-scheduler; do
done
```

* Take a look at what ports the services are running on.

```
# netstat -tulnp | grep -E "(kube)|(etcd)"
```

* Test etcd on the master (fed-master)

```
curl -s -L http://fed-master:4001/version
curl -s -L http://fed-master:4001/v2/keys/mykey -XPUT -d value="this is awesome" | python -mjson.tool
curl -s -L http://fed-master:4001/v2/keys/mykey | python -mjson.tool
curl -s -L http://fed-master:4001/v2/keys/mykey -XDELETE | python -mjson.tool
```

* Poke the kube-apiserver just a bit
```
curl -s -L http://fed-master:8080/version | python -mjson.tool
curl -s -L http://fed-master:8080/api/v1beta1/pods | python -mjson.tool
curl -s -L http://fed-master:8080/api/v1beta1/minions | python -mjson.tool
curl -s -L http://fed-master:8080/api/v1beta1/services | python -mjson.tool
```
**Configure the kubernetes services on the minion.**

***We need to configure the kubelet and start the kubelet and proxy***

* Edit /etc/kubernetes/kubelet to appear as such:

```
###
# kubernetes kubelet (minion) config

# The address for the info server to serve on
KUBELET_ADDRESS="--address=fed-minion"
KUBELET_ADDRESS="--address=0.0.0.0"

# The port for the info server to serve on
KUBELET_PORT="--port=10250"
Expand All @@ -189,11 +122,7 @@ for SERVICES in kube-proxy kubelet docker; do
done
```

* Take a look at what ports the services are running on.

```
netstat -tulnp | grep -E "(kube)|(docker)|(cadvisor)"
```
*You should be finished!*

* Check to make sure the cluster can see the minion (on fed-master)

Expand All @@ -203,106 +132,4 @@ kubectl get minions

**The cluster should be running! Launch a test pod.**

* Create a file on fed-master called apache.json that looks as such:

```
{
"apiVersion": "v1beta1",
"kind": "Pod",
"id": "apache",
"namespace": "default",
"labels": {
"name": "apache"
},
"desiredState": {
"manifest": {
"version": "v1beta1",
"id": "apache",
"volumes": null,
"containers": [
{
"name": "master",
"image": "fedora/apache",
"ports": [
{
"containerPort": 80,
"hostPort": 80,
"protocol": "TCP"
}
],
}
],
"restartPolicy": {
"always": {}
}
},
},
}
```

This json file is describing the attributes of the application environment. For example, it is giving it a "kind", "id", "name", "ports", and "image". Since the fedora/apache images doesn't exist in our environment yet, it will be pulled down automatically as part of the deployment process.

For more information about which options can go in the schema, check out the docs on the kubernetes github page.

* Deploy the fedora/apache image via the apache.json file.

```
kubectl create -f apache.json
```


* You can monitor progress of the operations with these commands:
On the master (fed-master) -

```
journalctl -f -l -xn -u kube-apiserver -u etcd -u kube-scheduler
```

* On the minion (fed-minion) -

```
journalctl -f -l -xn -u kubelet -u kube-proxy -u docker
```


* After the pod is deployed, you can also list the pod.

```
# /usr/bin/kubectl get pods
ID IMAGE(S) HOST LABELS STATUS
apache fedora/apache 192.168.121.65/ name=apache Running
```

The state might be 'Waiting'. This indicates that docker is still attempting to download and launch the container.

* You can get even more information about the pod like this.

```
kubectl get --output=json pods/apache | python -mjson.tool
```

* Finally, on the minion (fed-minion), check that the service is available, running, and functioning.

```
docker images
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE
kubernetes/pause latest 6c4579af347b 7 weeks ago 239.8 kB
fedora/apache latest 6927a389deb6 3 months ago 450.6 MB

docker ps -l
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
05c69c00ea48 fedora/apache:latest "/run-apache.sh" 2 minutes ago Up 2 minutes k8s--master.3f918229--apache.etcd--8cd6efe6_-_3a95_-_11e4_-_b618_-_5254005318cb--9bb78458

curl http://localhost
Apache
```

* To delete the container.

```
# /usr/bin/kubectl --server=http://fed-master:8080 delete pod apache
```

Of course this just scratches the surface. I recommend you head off to the kubernetes github page and follow the guestbook example. It's a bit more complicated but should expose you to more functionality.

You can play around with other Fedora images by building from Fedora Dockerfiles.
You should have a functional cluster, check out [101](https://github.com/GoogleCloudPlatform/kubernetes/blob/master/examples/walkthrough/README.md)!