Skip to content

Allow to configure the global topologicalKey for podAntiAffinity

What does this MR do?

To resolve high availability requirements in case of zone or region disaster, the user should be able to define a custom topologyKey on podAntiAffinity configuration based on his level BPC.

This MR add a new parameter to the global values : global.antiAffinityTopologyKey that allow to overwrite all topologyKey in the pod affinity section if the sub chart support it.

In addition, this MR enable support for podAntiAffinity on kas and gitlab-pages sub charts

Related issues

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion.

Required

  • Merge Request Title and Description are up to date, accurate, and descriptive
  • MR targeting the appropriate branch
  • MR has a green pipeline on GitLab.com

Expected (please provide an explanation if not completing)

  • Test plan indicating conditions for success has been posted and passes
  • Documentation created/updated
  • Tests added
  • Integration tests added to GitLab QA
  • Equivalent MR/issue for omnibus-gitlab opened
Edited by Hossein Pursultani

Merge request reports