Additional step when install GitLab Runner using KAS

What does this MR do?

We have a method to install GitLab Runner using Kubernetes Agent. In this method, we used helm template to generate the resources.

However, when running helm template --namespace target-namespace chart, the output doesn't include the namespace on the generated resources. Here is an example:

helm template --namespace gitlab-runner runner gitlab/gitlab-runner

# Source: gitlab-runner/templates/configmap.yaml
apiVersion: v1
kind: ConfigMap
metadata:
  name: runner-gitlab-runner
  labels:
    app: runner-gitlab-runner
    chart: gitlab-runner-0.31.0
    release: "runner"
    heritage: "Helm"

In this case, KAS will deploy GitLab Runner in the default namespace.

Here is the Github issue regarding this behavior of helm template: Closed helm template --namespace should set the 'metadata.namespace' field on created resources

As per this comment, it seems that there is no plan to fix this on the side of Helm.

Related issues

Author's checklist

• Consider taking the GitLab Technical Writing Fundamentals course
• Follow the:
  • Documentation process.
  • Documentation guidelines.
  • Style Guide.
• Ensure that the product tier badge is added to topic's h1.
• Request a review based on:
  • The documentation page's metadata.
  • The associated Technical Writer.

If you are only adding documentation, do not add any of the following labels:

• ~"feature"
• ~"frontend"
• ~"backend"
• ~"bug"
• ~"database"

These labels cause the MR to be added to code verification QA issues.

Review checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

• If the content requires it, ensure the information is reviewed by a subject matter expert.
• Technical writer review items:
  • Ensure docs metadata is present and up-to-date.
  • Ensure the appropriate labels are added to this MR.
  • If relevant to this MR, ensure content topic type principles are in use, including:
    • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
    • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
    • Any task steps should be written as a numbered list.
    • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
• Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
• Ensure a release milestone is set.