Jenkins-x on home kubernetes cluster

Jenkins-x appears to be the next big thing in CI/CD workflows – especially if you develop applications on kubernetes. There were a few tweaks I needed to do to set it up:

1. I had to manually create Persistent Volumes (no big deal, below are what I have for my NFS share)

   apiVersion: v1
   kind: PersistentVolume
   metadata:
     name: jenkins
     namespace: jx
     labels:
       app: jenkins
   spec:
     capacity:
       storage: 30Gi
     accessModes:
       - ReadWriteOnce
     nfs:
       server: 192.168.0.101
       path: "/volume1/k8s/jenkins/jenkins"
   ---
   apiVersion: v1
   kind: PersistentVolume
   metadata:
     name: jenkins-x-chartmuseum
     namespace: jx
     labels:
       app: jenkins-x-chartmuseum
   spec:
     capacity:
       storage: 100Gi
     accessModes:
       - ReadWriteOnce
     nfs:
       server: 192.168.0.101
       path: "/volume1/k8s/jenkins/jenkins-x-chartmuseum"
   ---
   apiVersion: v1
   kind: PersistentVolume
   metadata:
     name: jenkins-x-docker-registry
     namespace: jx
     labels:
       app: jenkins-x-docker-registry
   spec:
     capacity:
       storage: 30Gi
     accessModes:
       - ReadWriteOnce
     nfs:
       server: 192.168.0.101
       path: "/volume1/k8s/jenkins/jenkins-x-docker-registry"
   ---
   apiVersion: v1
   kind: PersistentVolume
   metadata:
     name: jenkins-x-mongodb
     namespace: jx
     labels:
       app: jenkins-x-mongodb
   spec:
     capacity:
       storage: 30Gi
     accessModes:
       - ReadWriteOnce
     nfs:
       server: 192.168.0.101
       path: "/volume1/k8s/jenkins/jenkins-x-mongodb"
   ---
   apiVersion: v1
   kind: PersistentVolume
   metadata:
     name: jenkins-x-nexus
     namespace: jx
     labels:
       app: jenkins-x-nexus
   spec:
     capacity:
       storage: 30Gi
     accessModes:
       - ReadWriteOnce
     nfs:
       server: 192.168.0.101
       path: "/volume1/k8s/jenkins/jenkins-x-nexus"

2. I had to modify the install line
   jx install --ingress-namespace ingress-nginx --domain wplr.rocks --tls-acme true --skip-ingress
3. I had to modify the jenkins-x-mongodb deployment to use image mongo:3.6.5-jessie. Still wonder why people use bitnami images.
4. I had to

   securityContext:
     runAsUser: 1024

   on the jenkins-x-nexus deployment. The container was trying to change permissions on my nfs mount. Not sure why my Synology NFS does not like permission changes.

Even after those changes, jenkins-x-monocular-ui still fails to start -_- … I have run out of time for now. More debugging to come later (MUCH MUCH later)