Infrastructure/ansible
1
0
Fork 0
Code Issues Pull requests 6 Projects Releases Packages Wiki Activity Actions

openshift-apps: fixup fedora-ostree-content-volume PV consumers

Browse source 
We can't share the same exact PV into two PVCs in different projects
but we can make two PVs for the same NFS share. Let's see if that
works.
This commit is contained in:
Dusty Mabe 2019-10-04 15:54:07 -04:00 • committed by Pierre-Yves Chibon
parent 7cfcdec33b
commit af7bd3386f
2 changed files with 8 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

6
roles/openshift-apps/coreos-ostree-importer/templates/pvc.yml
View file

@ -7,8 +7,10 @@ kind: PersistentVolumeClaim
metadata: metadata:
name: fedora-ostree-content-volume name: fedora-ostree-content-volume
spec: spec:
volumeName: "fedora-ostree-content-volume" # fedora-ostree-content-volume-1 is one of two PVs that share
# This values are mostly ignored since we're using a named # the fedora-ostree-content NetApp volume
volumeName: "fedora-ostree-content-volume-1"
# These values are mostly ignored since we're using a named
# volume, but are required. # volume, but are required.
accessModes: accessModes:
- ReadWriteMany - ReadWriteMany

6
roles/openshift-apps/fedora-ostree-pruner/templates/pvc.yml
View file

@ -7,8 +7,10 @@ kind: PersistentVolumeClaim
metadata: metadata:
name: fedora-ostree-content-volume name: fedora-ostree-content-volume
spec: spec:
volumeName: "fedora-ostree-content-volume" # fedora-ostree-content-volume-2 is one of two PVs that share
# This values are mostly ignored since we're using a named # the fedora-ostree-content NetApp volume
volumeName: "fedora-ostree-content-volume-2"
# These values are mostly ignored since we're using a named
# volume, but are required. # volume, but are required.
accessModes: accessModes:
- ReadWriteMany - ReadWriteMany