How to get started, and achieve tasks, using Kubernetes

Edit This Page

Fedora (Single Node)


  1. You need 2 or more machines with Fedora installed.


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 node (previously minion) working. Multiple nodes require a functional networking configuration 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 (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-node will be the node and run kubelet, proxy and docker.

System Information:


fed-master =
fed-node =

Prepare the hosts:

yum -y install --enablerepo=updates-testing kubernetes
yum -y install etcd iptables
echo "	fed-master	fed-node" >> /etc/hosts
# Comma separated list of nodes in the etcd cluster

# logging to stderr means we get it in the systemd journal

# journal message level, 0 is debug

# Should this cluster be allowed to run privileged docker containers
systemctl disable iptables-services firewalld
systemctl stop iptables-services firewalld

Configure the Kubernetes services on the master.

# The address on the local server to listen to.

# Comma separated list of nodes in the etcd cluster

# Address range to use for services

# Add your own!
mkdir /var/run/kubernetes
chown kube:kube /var/run/kubernetes
chmod 750 /var/run/kubernetes
for SERVICES in etcd kube-apiserver kube-controller-manager kube-scheduler; do
	systemctl restart $SERVICES
	systemctl enable $SERVICES
	systemctl status $SERVICES
    "apiVersion": "v1",
    "kind": "Node",
    "metadata": {
        "name": "fed-node",
        "labels":{ "name": "fed-node-label"}
    "spec": {
        "externalID": "fed-node"

Now create a node object internally in your Kubernetes cluster by running:

$ kubectl create -f ./node.json

$ kubectl get nodes
NAME                LABELS              STATUS
fed-node           name=fed-node-label     Unknown

Please note that in the above, it only creates a representation for the node fed-node internally. It does not provision the actual fed-node. Also, it is assumed that fed-node (as specified in name) can be resolved and is reachable from Kubernetes master node. This guide will discuss how to provision a Kubernetes node (fed-node) below.

Configure the Kubernetes services on the node.

We need to configure the kubelet on the node.

# Kubernetes kubelet (node) config

# The address for the info server to serve on (set to or "" for all interfaces)

# You may leave this blank to use the actual hostname

# location of the api-server

# Add your own!
for SERVICES in kube-proxy kubelet docker; do 
    systemctl restart $SERVICES
    systemctl enable $SERVICES
    systemctl status $SERVICES 
kubectl get nodes
NAME                LABELS              STATUS
fed-node          name=fed-node-label     Ready

To delete fed-node from your Kubernetes cluster, one should run the following on fed-master (Please do not do it, it is just for information):

kubectl delete -f ./node.json

You should be finished!

The cluster should be running! Launch a test pod.

You should have a functional cluster, check out 101!

Support Level

IaaS Provider Config. Mgmt OS Networking Docs Conforms Support Level
Bare-metal custom Fedora none docs   Project

For support level information on all solutions, see the Table of solutions chart.