Skip to content
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

DM-46898: Reconfigure RA for ComCam on sky #4071

Open
wants to merge 23 commits into
base: main
Choose a base branch
from

Conversation

mfisherlevine
Copy link
Contributor

No description provided.

Copy link
Contributor

@ctslater ctslater left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One inline suggestion to tighten up some syntax, overall looks good.

- name: {{ $.Release.Name }}-butler-secret
mountPath: {{ $.Values.butlerSecret.containerPath }}
{{- end }}
{{- if or $.Values.resources $script.resources }}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are a bunch of these ".values or script" blocks (nodeSelector, affinity, tolerations, etc), which I think can each be replaced by something like:

{{- if or $.Values.resources $script.resources }}
{{- $resources := $script.resources | default $.Values.resources }}
resources:
  {{- toYaml $resources | nindent 12 }}
{{- end }}

I've tried this out and it seems to behave correctly for all the combinations I could come up with. Or you could even inline it as {{- $script.resources | default $.Values.resources | toYaml | nindent 12}}, but I haven't tested that one. Still requires the if statement as a guard around the resources block.

chown 73006:73006 /secrets/*
chmod 0600 /secrets/*
volumeMounts:
- name: {{ $.Release.Name }}-raw-butler-secret
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why does this include $.Release.Name?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants