-
Notifications
You must be signed in to change notification settings - Fork 470
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
[kong] add nodeSelector to migration Jobs #238
Conversation
@@ -58,6 +58,10 @@ spec: | |||
{{- include "kong.volumeMounts" . | nindent 8 }} | |||
securityContext: | |||
{{- include "kong.podsecuritycontext" . | nindent 8 }} | |||
{{- if .Values.nodeSelector }} | |||
nodeSelector: | |||
{{ toYaml .Values.nodeSelector | indent 8 }} |
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.
Before this PR, all 3 edited files prefer nindent
(with {{-
) to indent
ing - this PR appears to be the first introduction of indent
.
Is there a rationale for breaking consistency? If not, could we do:
{{ toYaml .Values.nodeSelector | indent 8 }} | |
{{- toYaml .Values.nodeSelector | nindent 8 }} |
throughout this PR?
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.
Not really. Copy-pasta from the deployment template; newline-chomping convention isn't consistent throughout the templates.
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.
Conditional LGTM, assuming that the changes have been tested to work.
It's manual since we don't have an exhaustive test values.yaml with all non-default settings. I set it to an example value to confirm that the indentation is correct/didn't result in invalid Job resources rendering. |
What this PR does / why we need it:
The nodeSelector value was previously only applied to the main Deployment. It should be applied to migration Jobs also, since they run Kong also, and have the same platform requirements.
Which issue this PR fixes
(optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged)Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]
next
branch and targetsnext
, notmain
[kong]
)