GitLab custom runners with resource limits

We’re trying to configure custom runners inside our AKS cluster, which has a policy defined that every pod must have limits defined before starting.

I’ve successfully got the runenrs connected to the GitLab SaaS instance, but when I try and execute any step, I get the following error:

ERROR: Job failed (system failure): prepare environment: setting up build pod: admission webhook "validation.gatekeeper.sh" denied the request: [azurepolicy-container-limits-58cd4ab40ea8e76caf7d] container <init-permissions> has no resource limits. Check https://docs.gitlab.com/runner/shells/index.html#shell-profile-loading for more information

The runner has been installed via a Helm chart, and in the values.yaml file, we have:

runners:
  tags: aks-dev
  name: 'AKS-WL1-DEV-Cluster-noyj2'
  config: |
    [[runners]]
      [runners.kubernetes]
        image = "myPrivateImageRegistry/gitlab-runner/gitlab-runner-helper:x86_64-e0218c92"
        helper_image = "myPrivateImageRegistry/gitlab-runner/gitlab-runner-helper:x86_64-e0218c92"
        cpu_request = "100m"
        cpu_limit = "250m"
        helper_cpu_request = "100m"
        helper_cpu_limit = "250m"
        service_cpu_request = "100m"
        service_cpu_limit = "250m"
        memory_request = "128Mi"
        memory_limit = "256Mi"
        helper_memory_request = "128Mi"
        helper_memory_limit = "256Mi"
        service_memory_request = "128Mi"
        service_memory_limit = "256Mi"

How do I set the limits on the init-permissions container? Or is it incorrectly ignoring the limits that I’ve already specified?