This gist describes how to set up standalone kubelet + CRI-O + CNI on Fedora Core 31. The goal is to place a Kubernetes Pod manifest on an single node and access the application from the network. This guide has been tested on x86-64 and armv7 deployments.
Make sure the system is up to date:
dnf -y update
| { | |
| "apiVersion": "v1", | |
| "kind": "ImageStream", | |
| "metadata": { | |
| "annotations": { | |
| "openshift.io/display-name": "Go" | |
| }, | |
| "name": "golang" | |
| }, | |
| "spec": { |
| --- | |
| - name: Create partitions on master | |
| hosts: masters | |
| become: yes | |
| tasks: | |
| - name: Create LVEtcd logical volume | |
| lvol: | |
| lv: LVEtcd | |
| size: 10g |
| #!/bin/bash | |
| set -e | |
| set -o pipefail | |
| # Add user to k8s using service account, no RBAC (must create RBAC after this script) | |
| if [[ -z "$1" ]] || [[ -z "$2" ]]; then | |
| echo "usage: $0 <service_account_name> <namespace>" | |
| exit 1 | |
| fi |