1
0

fix (molgenis-vault): default cronjob schedule invalid

This commit is contained in:
Fleur Kelpin 2018-09-10 12:07:09 +02:00
parent 5b9b653601
commit 12de8ad404
2 changed files with 36 additions and 5 deletions

View File

@ -25,7 +25,7 @@ See [etcd-operator documentation](https://github.com/coreos/etcd-operator/blob/m
### Backup job
Define the schedule of the backup job
| Parameter | Description | Default |
| -------------------- | ---------------------------- | ------------------ |
| `backupJob.enable` | Enable backup cronjob | `true` |
| `backupJob.schedule` | cron schedule for the backup | `0 0 0 ? * MON *` |
| Parameter | Description | Default |
| -------------------- | ---------------------------- | ------------- |
| `backupJob.enable` | Enable backup cronjob | `true` |
| `backupJob.schedule` | cron schedule for the backup | `0 12 * * 1` |

View File

@ -16,7 +16,7 @@ backupJob:
# enable enables the backup job
enable: true
# schedule gives the cron schedule for the backup job
schedule: "0 0 0 ? * MON *"
schedule: "0 12 * * 1"
###
# All of the config variables related to setting up the etcd-operator
@ -45,3 +45,34 @@ etcd-operator:
image:
tag: v0.9.2
ui:
name: "vault-ui"
replicaCount: 1
image:
repository: djenriquez/vault-ui
tag: latest
service:
name: vault-ui
type: ClusterIP
externalPort: 8000
internalPort: 8000
# nodePort: 32001
ingress:
enabled: true
# Used to create Ingress record (should used with service.type: ClusterIP).
host: vault.molgenis.org
resources: {}
# We usually recommend not to specify default resources and to leave this as a conscious
# choice for the user. This also increases chances charts run on environments with little
# resources, such as Minikube. If you do want to specify resources, uncomment the following
# lines, adjust them as necessary, and remove the curly braces after 'resources:'.
# limits:
# cpu: 100m
# memory: 128Mi
#requests:
# cpu: 100m
# memory: 128Mi
nodeSelector: {}
vault:
auth: TOKEN