-
Notifications
You must be signed in to change notification settings - Fork 17
feat: helm: support adding affinity rule for coderd service #157
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
Conversation
This pull request has been linked to Shortcut Story #17413: enterprise-helm: add anti-affinity option to coderd deployment. |
{{- else }} | ||
{{- tpl (.value | toYaml) .context }} | ||
{{- end }} | ||
{{- end -}} |
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 is shamlessly lifted from Bitnami's charts repo :-)
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.
Seems to work for me
@khorne3 I know we autogenerate some docs for Helm values, I'm not sure if we need to note this anywhere, like in the release notes? Should be compatible with prior versions due to new defaults |
Yeah, release notes would be good. I'll add a mention to 1.24 changelog |
Thanks @khorne3 ! |
This PR adds the
coderd.affinity
configuration knob. This allows the user to specify any affinity they like for thecoderd
deployment. An example affinity is provided.