-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(HMS-1847): Adding configmap to job #691
fix(HMS-1847): Adding configmap to job #691
Conversation
111b764
to
64dd5d1
Compare
64dd5d1
to
b00146f
Compare
deploy/cloudwash_job.yaml
Outdated
- name: config-volume | ||
configMap: | ||
name: cloudwash-config | ||
envFrom: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This block shouldn't be necessary, the expected configmap is getting subPath mounted
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed the config map block only
did you mean the whole volume block?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just the envFrom
map - but the volumes
map is out of place too, its not part of Container spec, only volumeMounts
. volumes
is part of the Pod spec, that map starts at L20.
b00146f
to
dab55af
Compare
dab55af
to
212e189
Compare
/retest |
volumeMounts: | ||
- name: config-volume | ||
mountPath: /opt/app-root/src/cloudwash/settings.yaml | ||
subPath: settings.yaml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
suspect of this config with mountPath having the file, but I'm going to accept at this point to run in SRE cluster.
For adding config maps into a job:
3. Now have added its mount point in this MR's job file