sidekiq and webservice charts antiaffinity overwrite option
-
Please check this box if this contribution uses AI-generated content (including content generated by GitLab Duo features) as outlined in the GitLab DCO & CLA. As a benefit of being a GitLab Community Contributor, you receive complimentary access to GitLab Duo.
What does this MR do?
Allow you to override antiAffinity from global in sidekiq and webservice sub-chart, ignore the antiAffinity values from global chart, and set different affinity in webservice and sidekiq chart, like:
global:
antiAffinity: "hard"
affinity:
podAntiAffinity:
topologyKey: "global.test/hostname"
gitlab:
sidekiq:
antiAffinity: "soft"
affinity:
podAntiAffinity:
topologyKey: "sidekiq.test/hostname"
webservice:
antiAffinity: "soft"
affinity:
podAntiAffinity:
topologyKey: "webservice.test/hostname"
So, like if you want your gitlab component, like Gitaly, Praefect, shell, etc, deployed with antiAffinity: hard (requiredDuringSchedulingIgnoredDuringExecution) so you can't have multiple of these pods on the same node, but setting sidekiq/webservice antiAffinity: soft (preferredDuringSchedulingIgnoredDuringExecution), so change it to having one pod per node but having weight on it so in case you need more than your nodes running pods for loadbalancing, you abalbe to do it.
Related issues
Author checklist
For general guidance, please follow our Contributing guide.
Required
For anything in this list which will not be completed, please provide a reason in the MR discussion.
-
Merge Request Title and Description are up to date, accurate, and descriptive. -
MR targeting the appropriate branch. -
MR has a green pipeline. -
Documentation created/updated. -
Tests added/updated, and test plan for scenarios not covered by automated tests. -
Equivalent MR/issue for omnibus-gitlab opened.
Reviewers checklist
-
MR has a green pipeline on https://gitlab.com/gitlab-org/charts/gitlab. -
Consider downstream impact to the Operator, as per evaluating impact from changes to GitLab chart.