For guidance on the overall deprecations, removals and breaking changes workflow, please visit [Breaking changes, deprecations, and removing features](https://about.gitlab.com/handbook/product/gitlab-the-product/#breaking-changes-deprecations-and-removing-features) <!-- Use this template as a starting point for deprecations. --> ### Deprecation Summary In GitLab 13.6, the release of the [Allow user to specify any runner configuration in the runner helm chart](https://docs.gitlab.com/runner/install/kubernetes.html) feature meant that we deprecated values in the Helm Chart configuration that were specific to Runner. These fields are deprecated and will be removed in v1.0 of the Runner Helm Chart. | Field name | Description | | ------ |-----------------------------------------------------------------------------------------------------------------------------------------------| |image:| Define the GitLab Runner Image. Usage of a single URL is deprecated | |rbac.resources:| Define specific rbac permissions | |rbac.verbs:| Define specific rbac permissions | |runners.image:| Default container image to use for builds when none is specified | |runners.imagePullSecrets:| Specify one or more imagePullSecrets | |runners.imagePullPolicy:| Specify the image pull policy: never, if-not-present, always. The cluster default will be used if not set. | |runners.requestConcurrency:| Defines number of concurrent requests for new job from GitLab | |runners.privileged:| Enable or disable the privileged flag for all containers | |runners.namespace:| Namespace to run Kubernetes jobs in. Defaults to the namespace used for installing the Runner Manager. | |runners.pollTimeout: | The amount of time, in seconds, that needs to pass before the runner will timeout attempting to connect to the container it has just created. | |runners.outputLimit: | Set maximum build log size in kilobytes, by default set to 4096 (4MB). | |runners.cache.cacheType| Cache general settings | |runners.cache.cachePath| Cache general settings | |runners.cache.cacheShared| Cache general settings | |runners.cache.s3ServerAddress:| S3 settings | |runners.cache.s3BucketLocation:| S3 settings | |runners.cache.s3CacheInsecure:| S3 settings | |runners.cache.gcsBucketName:| GCS settings | |runners.builds:| (Property and all sub-properties) Build Container specific configuration | |runners.services:| (Property and all sub-properties) Service Container specific configuration. | |runners.helpers:| (Property and all sub-properties) Helper Container specific configuration. | |runners.pod_security_context:| (Property and all sub-properties) Helper container security context configuration. | |runners.serviceAccountName:| Service Account to be used for runners. | |runners.cloneUrl:| If GitLab is not reachable through $CI_SERVER_URL. | |runners.nodeSelector:| (Property and all sub-properties) Specify node labels for CI job pods assignment | |runners.nodeTolerations:| (Property and all sub-properties) Specify node tolerations for CI job pods assignment. | |runners.podLabels:| (Property and all sub-properties) Specify pod labels for CI job pods | |runners.podAnnotations:| (Property and all sub-properties) Specify annotations for job pods. | |runners.env:| Configure environment variables that will be injected to the pods that are created while the build is running. | <!-- This should contain a brief description of the feature or functionality that is deprecated. The description should clearly state the potential impact of the deprecation to end users. It is recommended that you link to the documentation. The description of the deprecation should state what actions the user should take to rectify the behavior. If the deprecation is scheduled for an upcoming release, the content should remain in the deprecations documentation page until it has been completed. For example, if a deprecation is announced in 14.9 and scheduled to be completed in 15.0, the same content would be included in the documentation for 14.9, 14.10, and 15.0. **If this issue proposes a breaking change outside a major release XX.0, you need to get approval from your manager and request collaboration from Product Operations on communication. Be sure to follow the guidance [here](https://about.gitlab.com/handbook/product/gitlab-the-product/#breaking-changes-deprecations-and-removing-features.)** --> ### Breaking Change <!-- Does this MR contain a breaking change? If yes: - Add the ~"breaking change" label to this issue. - Add instructions for how users can update their workflow. --> ### Affected Topology - GitLab SaaS - GitLab Self-Managed **Note**: The impact is specifically to those customers who self-manage runners and use the Helm chart for installing and configuring the Runner on Kubernetes. <!-- Who is affected by this deprecation, Self-managed users, SaaS users, or both? This is especially important when nearing the annual major release where breaking changes and removals are typically introduced. These changes might be seen on GitLab.com before the official release date. --> ### Affected Tier * Free * Premium * Ultimate <!-- Which tier is this feature available in? * Free * Premium * Ultimate --> ### Checklists **Labels** - [x] This issue is labeled ~deprecation, and with the relevant `~devops::`, `~group::`, and `~Category:` labels. - [x] This issue is labeled ~"breaking change" if the removal of the deprecated item will be a [breaking change](https://about.gitlab.com/handbook/product/gitlab-the-product/#examples-of-breaking-changes). **Timeline** Please add links to the relevant merge requests. - As soon as possible, but no later than the third milestone preceding the major release (for example, given the following release schedule: `14.8, 14.9, 14.10, 15.0` – `14.8` is the third milestone preceding the major release): - [x] A [deprecation announcement entry](https://about.gitlab.com/handbook/marketing/blog/release-posts/#creating-a-deprecation-announcement) has been created so the deprecation will appear in release posts and on the [general deprecation page](https://docs.gitlab.com/ee/update/deprecations). - [x] Documentation has been updated to mark the feature as [deprecated](https://docs.gitlab.com/ee/development/documentation/versions.html#deprecations-and-removals). - [ ] On or before the major milestone: A [removal entry](https://about.gitlab.com/handbook/marketing/blog/release-posts/#removals) has been created so the removal will appear on the [removals by milestones](https://docs.gitlab.com/ee/update/removals) page and be announced in the release post. - On the major milestone: - [ ] The deprecated item has been removed. - [ ] If the removal of the deprecated item is a [breaking change](https://about.gitlab.com/handbook/product/gitlab-the-product/#examples-of-breaking-changes), the merge request is labeled ~"breaking change". **Mentions** - [ ] Your stage's stable counterparts have been `@mentioned` on this issue. For example, Customer Support, Customer Success (Technical Account Manager), Product Marketing Manager. - To see who the stable counterparts are for a product team visit [product categories](https://about.gitlab.com/handbook/product/categories/) - If there is no stable counterpart listed for Sales/CS please mention `@timtams` - If there is no stable counterpart listed for Support please mention `@gitlab-com/support/managers` - If there is no stable counterpart listed for Marketing please mention `@cfoster3` - [x] Your GPM has been `@mentioned` so that they are aware of planned deprecations. The goal is to have reviews happen at least two releases before the final removal of the feature or introduction of a breaking change. ### Deprecation Milestone <!-- In which milestone will this deprecation be announced ? --> 15.6 ### Planned Removal Milestone <!-- In which milestone will the feature or functionality be removed and announced? --> 16.0 ### Links <!-- Add links to any relevant documentation or code that will provide additional details or clarity regarding the planned change. This issue is the main SSOT for the deprecations and removals process. Be sure to link all issues and MRs related to this deprecation/removal to this issue. This can include removal issues that were created ahead of time, and the MRs doing the actual deprecation/removal work. --> <!-- Label reminders - you should have one of each of the following labels. Use the following resources to find the appropriate labels: - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ --> <!-- Populate the Section, Group, and Category --> <!-- Choose the Pricing Tier(s) --> <!-- Identifies that this Issue is related to deprecating a feature --> <!-- Add the ~"breaking change" label to this issue if necessary -->