Skip to content

Remove duplicate declaration of `nodeSelector` in Kas

What does this MR do?

Due to having two MRs being worked on at the same time (which both got merged), we now specify the nodeSelector on the kas deployment twice. This cleans up one of them.

As the setting itself is still valid, it should remain documented etc.

Related issues

Closes #2608 (closed)

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

Merge request reports