Jenkins fail to start on AWS with HA k8s installation using multiple AZ's

[rasheedamir]

Jenkins pod fails to start on AWS with HA k8s installation using multiple AZ's

• Cloud Provider: AWS
• fabric8 installer: gofabric8 install
• Error: No nodes are available that match all of the following predicates:: NoVolumeZoneConflict (2)

As fabric8 is provisioning Jenkins which provisions 2 PVCs which are used by a single pod. My nodes are in AZs eu-west-1a and eu-west-1b. The dynamically created PVs are each created in a random AZ (I assume either eu-west-1a or eu-west-1b) so the pod can only be created if all the PVs by chance happen to be created in the same AZ. Since they're created in different AZs so there's no one AZ the pod can be created in which satisfies the NoVolumeZoneConflict predicate.

@rawlingsj @jstrachan have suggested a solution to delete the jenkins pod and create again with single PVC:

kubectl delete deployment jenkins

kubectl apply -f https://gist.githubusercontent.com/rawlingsj/68ba3437207bd38fd8202ec708d580df/raw/f53e917d3c3f744d666e825760fa0539c67a25e8/gistfile1.txt

[rasheedamir]

k8s issue: https://github.com/kubernetes/kubernetes/issues/39178

Until the issue is resolved we should just attach one PVC to a pod!

[vinayagg]

The issue with that approach is, when I uninstall the project, it deletes PV and PVC, thus losing all the data.