-
egon w. stemle authored
We noticed the subprocess that runs our 'cron' sometimes quits silently; one possibility we see is that OOM kills it. In any case, we now also check for the existence of the commands `sleep` or `timeout` in the process table (`ps`) via the `livenessProbe`. Address #60
egon w. stemle authoredWe noticed the subprocess that runs our 'cron' sometimes quits silently; one possibility we see is that OOM kills it. In any case, we now also check for the existence of the commands `sleep` or `timeout` in the process table (`ps`) via the `livenessProbe`. Address #60
dspace-deployment.yaml 2.82 KiB
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
annotations:
kompose.cmd: kompose convert
kompose.version: 1.3.0 (4f187a1)
creationTimestamp: null
labels:
io.kompose.service: dspace
name: dspace
namespace: dspace-dev
spec:
replicas: 1
strategy: {}
template:
metadata:
creationTimestamp: null
labels:
io.kompose.service: dspace
spec:
initContainers:
- image: postgres
name: clarin-dspace-check-db-ready
command: ['sh', '-c',
'until pg_isready -h postgres -p 5432;
do echo waiting for database; sleep 2; done;']
containers:
- env:
- name: DSPACE_USER
valueFrom:
secretKeyRef:
key: dspace.user
name: dspace-secrets
- name: DSPACE_PASSWORD
valueFrom:
secretKeyRef:
key: dspace.pass
name: dspace-secrets
- name: DSPACE_DBNAME
valueFrom:
secretKeyRef:
key: dspace.db.name
name: dspace-secrets
- name: DSPACE_UTILSDBNAME
valueFrom:
secretKeyRef:
key: dspace.utils.name
name: dspace-secrets
- name: MAIL_USER
valueFrom:
secretKeyRef:
key: mail.user
name: dspace-secrets
- name: MAIL_PASSWORD
valueFrom:
secretKeyRef:
key: mail.pass
name: dspace-secrets
image: gitlab.inf.unibz.it:4567/commul/docker/clarin-dspace/staging/dspace:1.3.3-RC1
name: clarin-dspace
imagePullPolicy: Always
ports:
- containerPort: 8009
- containerPort: 8080
- containerPort: 8000
- containerPort: 2641
resources: {}
volumeMounts:
- mountPath: /opt/lindat-dspace/installation/assetstore
name: dspace-assetstore