Commit dfe8ddea authored by Suzanne Selhorn's avatar Suzanne Selhorn

Merge branch 'verify-runner-ssh-disable-strict-host-key-deprecation' into 'master'

Verify Runner disable_strict_host_key_checking deprecation

See merge request gitlab-org/gitlab!73892
parents 0462b2b1 8ecdc14d
- name: "Known host required for GitLab Runner SSH executor"
announcement_milestone: "14.5" # The milestone when this feature was first announced as deprecated.
announcement_date: "2021-11-22"
removal_milestone: "15.0" # the milestone when this feature is planned to be removed
body: | # Do not modify this line, instead modify the lines below.
In [GitLab 14.3](https://gitlab.com/gitlab-org/gitlab-runner/-/merge_requests/3074), we added a configuration setting in the GitLab Runner config.toml. This setting, [`[runners.ssh.disable_strict_host_key_checking]`](https://docs.gitlab.com/runner/executors/ssh.html#security), controls whether or not to use strict host key checking with the SSH executor.
In GitLab 15.0 and later, the default value for this configuration option will change from `true` to `false`. This means that strict host key checking will be enforced when using the GitLab Runner SSH executor.
stage: Verify
tiers: [Core, Premium, Ultimate]
issue_url: https://gitlab.com/gitlab-org/gitlab-runner/-/issues/28192
documentation_url: https://docs.gitlab.com/runner/executors/ssh.html#security
...@@ -22,9 +22,10 @@ located at `lib/tasks/gitlab/docs/compile_deprecations.rake`. ...@@ -22,9 +22,10 @@ located at `lib/tasks/gitlab/docs/compile_deprecations.rake`.
Do not edit this page directly. Do not edit this page directly.
To add a deprecation, follow the [deprecation item guidance](https://about.gitlab.com/handbook/marketing/blog/release-posts/#creating-a-deprecation-entry) and use the [`/data/deprecations/templates/example.yml`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/data/deprecations/templates/example.yml) file as a template. To add a deprecation, use the example.yml file in `/data/deprecations/templates` as a template.
To update this doc, follow the instructions in [Update the deprecations doc](https://about.gitlab.com/handbook/marketing/blog/release-posts/#update-the-deprecations-doc). To update this doc, run `bin/rake gitlab:docs:compile_deprecations`.
To verify this doc is up to date, run `bin/rake gitlab:docs:check_deprecations`
--> -->
## 14.4 ## 14.4
...@@ -85,6 +86,19 @@ Note that we are not deprecating the Kerberos SPNEGO integration, only the old p ...@@ -85,6 +86,19 @@ Note that we are not deprecating the Kerberos SPNEGO integration, only the old p
Announced: 2021-09-22 Announced: 2021-09-22
### REST API Runner will not contain 'paused'
Runner REST API will not return "paused" as a status in GitLab 15.0.
REST API: Paused runners' status will only relate to runner contact status, such as:
"online", "offline", "not_connected". Status "paused" will not appear when the runner is
not active.
When checking if a runner is "paused", API users are advised to check the boolean attribute
"active" to be `false` instead.
Announced:
## 15.2 ## 15.2
### NFS for Git repository storage deprecated ### NFS for Git repository storage deprecated
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment