Add commits to configuration to deploy :latest tag

The recommended way to update a kubernetes deployment to a new image is
to change the image tag. However, our build server is configured to push
every commit of the `master` branch to docker hub to the respective
repository and tag `:latest`. So adding some configuration that can be
changed seems to be a trick to re-deploy the `:latest` image.

See here:
https://stackoverflow.com/a/51835397
This commit is contained in:
Robert Schäfer 2019-02-01 18:50:30 +01:00
parent ad3a974076
commit 6fed4797ed
4 changed files with 12 additions and 3 deletions

View File

@ -18,6 +18,8 @@ spec:
spec:
containers:
- env:
- name: COMMIT
value: <BACKEND_COMMIT>
- name: MOCK
value: "false"
- name: CLIENT_URI

View File

@ -19,6 +19,8 @@
spec:
containers:
- env:
- name: COMMIT
value: <BACKEND_COMMIT>
- name: SSH_USERNAME
valueFrom:
configMapKeyRef:
@ -64,7 +66,6 @@
name: ssh-keys-directory
- mountPath: /mongo-export/
name: mongo-export
restartPolicy: Always
volumes:
- name: ssh-keys-directory
persistentVolumeClaim:
@ -72,6 +73,7 @@
- name: mongo-export
persistentVolumeClaim:
claimName: mongo-export-claim
restartPolicy: Always
terminationGracePeriodSeconds: 30
status: {}
---

View File

@ -18,6 +18,8 @@
spec:
containers:
- env:
- name: COMMIT
value: <BACKEND_COMMIT>
- name: NEO4J_apoc_import_file_enabled
value: "true"
- name: NEO4J_dbms_memory_pagecache_size
@ -47,13 +49,12 @@
- containerPort: 7687
- containerPort: 7474
resources: {}
imagePullPolicy: IfNotPresent
imagePullPolicy: Always
volumeMounts:
- mountPath: /data/
name: neo4j-data
- mountPath: /mongo-export/
name: mongo-export
restartPolicy: Always
volumes:
- name: mongo-export
persistentVolumeClaim:
@ -61,6 +62,8 @@
- name: neo4j-data
persistentVolumeClaim:
claimName: neo4j-data-claim
restartPolicy: Always
terminationGracePeriodSeconds: 30
status: {}
---
apiVersion: v1

View File

@ -18,6 +18,8 @@ spec:
spec:
containers:
- env:
- name: COMMIT
value: <WEBAPP_COMMIT>
- name: HOST
value: 0.0.0.0
- name: BACKEND_URL