Docs feedback: GitLab Runner Helm Chart - secret creation examples missing namespace

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

  • Close this issue

Problem to solve

I prefer Runners cache connection created with Kubernetes secret. Documentation is almost right but it doesn't tell that secret should be in the same namespace with runner (maybe this is obvious to someone who masters Kubernetes).

Documentation: GitLab Runner Helm Chart

Further details

I've tested this only in GCP. Probably same behaviour in other environments.

Debugging is also hard. If secret is configured to runner but doesn't exist in the same namespace the runner just hangs in "ContainerCreation" -stage and problem stays in mystery.

Proposal

Add --namespace <RUNNERS_NAMESPACE> to shell snippet

Example:

kubectl create secret --namespace <RUNNERS_NAMESPACE> generic gcsaccess \
    --from-literal=gcs-access-id="YourAccessID" \
    --from-literal=gcs-private-key="YourPrivateKey"

Who can address the issue

Somebody who has access to modify documentation

Other links/references

Link the doc and describe what is wrong with it.

Secret creation examples missing namespace GitLab Runner Helm Chart

Edited Sep 23, 2025 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading