Here are my notes for setting up the SIG’s nfs-provisioner. You should follow these directions to setup the nfs-provisioner kubernetes-sigs/nfs-subdir-external-provisioner.

1. Clone the nfs-subdir-external-provisioner

git clone https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner.git

2. If you haven’t already, you may need to create the nfs-provisioner namespace.

a. Create the ns.yaml

apiVersion: v1
kind: Namespace
metadata:
  labels:
    kubernetes.io/metadata.name: nfs-provisioner
    pod-security.kubernetes.io/enforce: privileged
    pod-security.kubernetes.io/enforce-version: v1.24
  name: nfs-provisioner

b. create the namespace

oc apply -f ns.yaml

c. annotate the namespace

oc label namespace/nfs-provisioner security.openshift.io/scc.podSecurityLabelSync=false --overwrite=true
oc label namespace/nfs-provisioner pod-security.kubernetes.io/enforce=privileged --overwrite=true
oc label namespace/nfs-provisioner pod-security.kubernetes.io/audit=privileged --overwrite=true
oc label namespace/nfs-provisioner pod-security.kubernetes.io/warn=privileged --overwrite=true

3. Change to the deploy/ directory

cd nfs-subdir-external-provisioner/deploy

4. Update the namespace default to nfs-provisioner for deployment.yaml

5. On the Bastion server, look at ocp4-helpernode/helpernode_vars.yaml for the helper.ipaddr value.

helper:
  networkifacename: env3
  name: "bastion-0"
  ipaddr: "193.168.200.15"

6. Update the deployment with the NFS_SERVER using the helper.ipaddr and the NFS_PATH /export. It should look like the following:

    spec:
      serviceAccountName: nfs-client-provisioner
      containers:
        - name: nfs-client-provisioner
          image: k8s.gcr.io/sig-storage/nfs-subdir-external-provisioner:v4.0.2
          volumeMounts:
            - name: nfs-client-root
              mountPath: /persistentvolumes
          env:
            - name: PROVISIONER_NAME
              value: k8s-sigs.io/nfs-subdir-external-provisioner
            - name: NFS_SERVER
              value: 193.168.200.15
            - name: NFS_PATH
              value: /export
      volumes:
        - name: nfs-client-root
          nfs:
            server: 193.168.200.15
            path: /export

v4.0.2 supports ppc64le.

Be sure to remove the namespace: default

7. Create the deployment

oc apply -f deployment.yaml
deployment.apps/nfs-client-provisioner created

8. Get the pods

oc get pods
NAME                                     READY   STATUS    RESTARTS   AGE
nfs-client-provisioner-b8764c6bb-mjnq9   1/1     Running   0          36s

9. Setup Authorization

NAMESPACE=`oc project -q`
sed -i'' "s/namespace:.*/namespace: $NAMESPACE/g" ./rbac.yaml 
oc create -f rbac.yaml
oc adm policy add-scc-to-user hostmount-anyuid system:serviceaccount:$NAMESPACE:nfs-client-provisioner

10. Create the storage class file

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: nfs-client
provisioner: k8s-sigs.io/nfs-subdir-external-provisioner # or choose another name, must match deployment's env PROVISIONER_NAME'
parameters:
  pathPattern: "${.PVC.namespace}/${.PVC.annotations.nfs.io/storage-path}" # waits for nfs.io/storage-path annotation, if not specified will accept as empty string.
  onDelete: delete

11. Apply the StorageClass

oc apply -f sc.yml

12. Then you can deploy the PV and PVC files/6_EvictPodsWithPVC_dp.yml

References

• git repo

Per the IBM Cloud Kubernetes cluster-api provider, I followed the raw instructions with some amendments.

Steps

1. Provision an Ubuntu 20.04 image.

2. Update the apt repository

$ apt update

3. Install the dependencies (more than what’s in the instructions)

$ apt install qemu-kvm libvirt-daemon-system libvirt-clients virtinst cpu-checker libguestfs-tools libosinfo-bin make git unzip ansible python3-pip

4. Clone the image-builder repo

$ git clone https://github.com/kubernetes-sigs/image-builder.git

5. Change to the capi image

$ cd image-builder/images/capi

6. Make the deps-raw to confirm everything is working.

$ make deps-raw

7. Create the ubuntu-2004 image.

$ make build-qemu-ubuntu-2004

Once complete you’ll see:

==> qemu: Running post-processor: custom-post-processor (type shell-local)
==> qemu (shell-local): Running local shell script: /tmp/packer-shell078717884
Build 'qemu' finished after 12 minutes 8 seconds.

==> Wait completed after 12 minutes 8 seconds

==> Builds finished. The artifacts of successful builds are:
--> qemu: VM files in directory: ./output/ubuntu-2004-kube-v1.22.9
--> qemu: VM files in directory: ./output/ubuntu-2004-kube-v1.22.9

8. Append the .qcow2 extension

$ mv ./output/ubuntu-2004-kube-v1.22.9/ubuntu-2004-kube-v1.22.9 ./output/ubuntu-2004-kube-v1.22.9/ubuntu-2004-kube-v1.22.9.qcow2

You can now upload the output to IBM Cloud Object Storage.

A couple quick tips:

• If you see any warnings, you can get advanced details using export PACKER_LOG=1 which puts out the full packer logging. see Packer
• KVM module not found indicates you are running in a nested KVM, you’ll have to swap out of the VM and enable nested KVM. Fedora: Docs
• Adding a VM to VPC is documented here Console: customImage

The Red Hat Ecosystem Catalog contains a supported version of the pause container. This container is based on ubi8. This best version of the Pause container to use for multiarch purposes.

Don’t use docker.io/ibmcom/pause-ppc64le:3.1 when you have a multi-architecture version

Steps

1. Create a Pod yaml pointing to the Red Hat registry.

$ cat << EOF > pod.yaml 
kind: Pod
apiVersion: v1
metadata:
  name: demopod-1
  labels:
    demo: foo
spec:
  containers:
  - name: pause
    image: registry.access.redhat.com/ubi8/pause:latest
EOF

2. Create the Pod

$ oc apply -f pod.yaml 
pod/demopod-1 created

3. Check the Pod is running.

$ oc get pods -l demo=foo
NAME        READY   STATUS    RESTARTS   AGE
demopod-1   1/1     Running   0          89s

You have a Pause container running in OpenShift.