GitLab runner cache configuration for Kubernetes deployed runner (GitLab managed app on GitLab.com)

Problem to solve

We are using GitLab.com with the Silver-Plan and manage some Kubernetes Clusters. In one of these clusters, we have a GitLab Runner installed (using the GitLab integrated Applications handling).

But we miss the ability to configure caching for the runner.
How can we configure the GCS setting?
Is there any UI for this?

Intended users

Unknown

Further details

It might be helpful to get an UI to set up the runner configuration with the following abilities:

  • Cache configuration (type, bucket name, credentials)
  • Concurrent configuration (integer)

Proposal

Permissions and Security

Documentation

Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Links / references

Assignee Loading
Time tracking Loading