GitLab agent for Kubernetes fails to deploy to multiple namespaces

Summary

We are currently trialling GitLab's cluster management as a way to manage our Gitlab CI runner setup. In our case, each team utilising Gitlab CI has a dedicated namespace, runner and collection of worker nodes. This is achieved using the cluster management project and registering the agent to that project.

In addition to this process, we have a common set of resources that we want to apply to every namespace associated with GitLab CI - these are located in a common directory in the cluster management project, but it seems the cluster config file doesn't allow for applying the same set of resources multiple times. I tried:

gitops:
  # Manifest projects are watched by the agent. Whenever a project changes,
  # GitLab deploys the changes using the agent.
  
  manifest_projects:
  - id: my-group/ci-prod-cluster-configuration
    default_namespace: gitlab-ci-prod-1
    # Paths inside of the repository to scan for manifest files.
    # Directories with names starting with a dot are ignored.
    paths:
    - glob: 'applications/gitlab-runner-default/additional-resources/gitlab-ci-*.yaml'
  - id: my-group/ci-prod-cluster-configuration
    default_namespace: gitlab-ci-prod-2
    # Paths inside of the repository to scan for manifest files.
    # Directories with names starting with a dot are ignored.
    paths:
    - glob: 'applications/gitlab-runner-default/additional-resources/gitlab-ci-*.yaml'

But this approach only synchronises the first namespace, not the second.

Steps to reproduce

Example Project

What is the current bug behavior?

What is the expected correct behavior?

Relevant logs and/or screenshots

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info 

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)


(we will only investigate if the tests are passing)

Possible fixes