alosadagrande

plan: hub-cluster
force: true
version: stable
tag: "4.11.13"
provisioning_enable: false
virtual_masters: false
virtual_workers: false
launch_steps: true
deploy_openshift: true
cluster: "hub"

alosadagrande

apiVersion: v1
items:
- apiVersion: k8s.cni.cncf.io/v1
  kind: NetworkAttachmentDefinition
  metadata:
    annotations:
      k8s.v1.cni.cncf.io/resourceName: openshift.io/xxv710_1
    name: sriov-network
    namespace: vfio-scc 
  spec:

alosadagrande

apiVersion: ptp.openshift.io/v1
kind: PtpConfig
metadata:
  name: slave
  namespace: openshift-ptp
spec:
  profile:
  - name: "slave"
    interface: "eno1"
    ptp4lOpts: "-2 -s --summary_interval -4"

alosadagrande

apiVersion: ptp.openshift.io/v1
kind: PtpConfig
metadata:
  name: boundaryclock
  namespace: openshift-ptp
spec:
  profile:
  - name: "bc"
    interface: ""
    ptp4lOpts: "-2 --summary_interval -4"

alosadagrande

apiVersion: ptp.openshift.io/v1
kind: PtpConfig
metadata:
  name: grandmaster
  namespace: openshift-ptp
spec:
  profile:
  - interface: ens5f1
    name: grandmaster
    phc2sysOpts: "-a -r -r -n 24"

alosadagrande

Using Sushy Tools with Libvirt

• Add linux user to libvirt group

sudo usermod -a -G libvirt <your-user>
sudo -y install libvirt-devel

• Login and validate user can execute virsh commands

alosadagrande

What is this about?

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.

Prepare the system

Make sure the system is up to date:

dnf -y update

alosadagrande

[root@kubevirt-alosadag-nested ~]# kubectl logs -f importer-fedora-fkq6b
I1016 11:18:39.356054       1 importer.go:51] Starting importer
I1016 11:18:39.356400       1 importer.go:107] begin import process
I1016 11:18:40.299369       1 data-processor.go:252] Calculating available size
I1016 11:18:40.303676       1 data-processor.go:260] Checking out file system volume size.
I1016 11:18:40.303705       1 data-processor.go:264] Request image size not empty.
I1016 11:18:40.303727       1 data-processor.go:269] Target size 4Gi.
I1016 11:18:40.310391       1 data-processor.go:182] New phase: Convert
I1016 11:18:40.310420       1 data-processor.go:188] Validating image
I1016 11:18:41.495540       1 qemu.go:212] 0.00

alosadagrande

{
  "apiVersion": "v1",
  "kind": "ResourceQuota",
  "metadata": {
    "name": "test-quota"
  },
  "spec": {
    "hard": {
      "memory": "1Gi",
      "cpu": "2",

alosadagrande

apiVersion: v1
items:
- apiVersion: v1
  kind: LimitRange
  metadata:
    creationTimestamp: null
    name: limits-prod
  spec:
    limits:
    - max: