Try with less config
This commit is contained in:
parent
12a9d898da
commit
395d4daa7a
|
@ -6,6 +6,5 @@ patchesStrategicMerge:
|
||||||
- nextcloud-deployment.yml
|
- nextcloud-deployment.yml
|
||||||
- nextcloud-ingress.yml
|
- nextcloud-ingress.yml
|
||||||
- nextcloud-namespace.yml
|
- nextcloud-namespace.yml
|
||||||
- nextcloud-pvc.yml
|
|
||||||
- nextcloud-service.yml
|
- nextcloud-service.yml
|
||||||
- s3-service.yml
|
- s3-service.yml
|
||||||
|
|
|
@ -1,34 +1,11 @@
|
||||||
---
|
---
|
||||||
kind: Deployment
|
kind: Deployment
|
||||||
apiVersion: apps/v1
|
apiVersion: apps/v1
|
||||||
metadata:
|
|
||||||
name: vr-node
|
|
||||||
namespace: vr
|
|
||||||
labels:
|
|
||||||
app: vr-node
|
|
||||||
spec:
|
spec:
|
||||||
replicas: 1
|
|
||||||
selector:
|
|
||||||
matchLabels:
|
|
||||||
app: vr-node
|
|
||||||
template:
|
template:
|
||||||
metadata:
|
|
||||||
creationTimestamp:
|
|
||||||
labels:
|
|
||||||
app: vr-node
|
|
||||||
spec:
|
spec:
|
||||||
volumes:
|
|
||||||
- name: server-storage
|
|
||||||
persistentVolumeClaim:
|
|
||||||
claimName: vr-shared-storage-claim
|
|
||||||
containers:
|
containers:
|
||||||
- name: vr
|
- env:
|
||||||
image: docker.sunet.se/drive/nextcloud-custom:25.0.3.3-4
|
|
||||||
volumeMounts:
|
|
||||||
- name: server-storage
|
|
||||||
mountPath: /var/www/html
|
|
||||||
subPath: server-data
|
|
||||||
env:
|
|
||||||
- name: GSS_MASTER_URL
|
- name: GSS_MASTER_URL
|
||||||
value: "https://drive.test.sunet.se"
|
value: "https://drive.test.sunet.se"
|
||||||
- name: LOOKUP_SERVER
|
- name: LOOKUP_SERVER
|
||||||
|
|
|
@ -1,15 +0,0 @@
|
||||||
---
|
|
||||||
kind: PersistentVolumeClaim
|
|
||||||
apiVersion: v1
|
|
||||||
metadata:
|
|
||||||
name: vr-shared-storage-claim
|
|
||||||
namespace: vr
|
|
||||||
annotations:
|
|
||||||
volume.beta.kubernetes.io/storage-class: openebs-jiva-3repl
|
|
||||||
spec:
|
|
||||||
storageClassName: openebs-jiva-3repl
|
|
||||||
accessModes:
|
|
||||||
- ReadWriteOnce
|
|
||||||
resources:
|
|
||||||
requests:
|
|
||||||
storage: 5G
|
|
Loading…
Reference in a new issue