Merge branch 'axil-task-runner-toolbox' into 'master'

Replace task-runner with toolbox

See merge request gitlab-org/gitlab!77366

doc/administration/troubleshooting/kubernetes_cheat_sheet.md

@@ -118,15 +118,18 @@ and they will assist you with any issues you are having.
   kubectl get events -w --namespace=gitlab
   ```
 
-- Most of the useful GitLab tools (console, Rake tasks, etc) are found in the task-runner
-  pod. You may enter it and run commands inside or run them from the outside:
+- Most of the useful GitLab tools (console, Rake tasks, etc) are found in the toolbox
+  pod. You may enter it and run commands inside or run them from the outside.
+
+  NOTE:
+  The `task-runner` pod was renamed to `toolbox` in GitLab 14.2 (charts 5.2).
 
   ```shell
   # find the pod
-  kubectl get pods | grep task-runner
+  kubectl --namespace gitlab get pods -lapp=toolbox
 
   # enter it
-  kubectl exec -it <task-runner-pod-name> -- bash
+  kubectl exec -it <toolbox-pod-name> -- bash
 
   # open rails console
   # rails console can be also called from other GitLab pods
@@ -139,10 +142,10 @@ and they will assist you with any issues you are having.
   /usr/local/bin/gitlab-rake gitlab:check
 
   # open console without entering pod
-  kubectl exec -it <task-runner-pod-name> -- /srv/gitlab/bin/rails console
+  kubectl exec -it <toolbox-pod-name> -- /srv/gitlab/bin/rails console
 
   # check the status of DB migrations
-  kubectl exec -it <task-runner-pod-name> -- /usr/local/bin/gitlab-rake db:migrate:status
+  kubectl exec -it <toolbox-pod-name> -- /usr/local/bin/gitlab-rake db:migrate:status
   ```
 
   You can also use `gitlab-rake`, instead of `/usr/local/bin/gitlab-rake`.
@@ -163,12 +166,15 @@ and they will assist you with any issues you are having.
   kubectl get secret <secret-name> -ojsonpath={.data.password} | base64 --decode ; echo
   ```
 
-- How to connect to a GitLab PostgreSQL database:
+- How to connect to a GitLab PostgreSQL database.
+
+  NOTE:
+  The `task-runner` pod was renamed to `toolbox` in GitLab 14.2 (charts 5.2).
 
   In GitLab 14.2 (chart 5.2) and later:
 
   ```shell
-  kubectl exec -it <task-runner-pod-name> -- /srv/gitlab/bin/rails dbconsole --include-password --database main
+  kubectl exec -it <toolbox-pod-name> -- /srv/gitlab/bin/rails dbconsole --include-password --database main
   ```
 
   In GitLab 14.1 (chart 5.1) and earlier:

doc/raketasks/backup_restore.md

@@ -115,12 +115,8 @@ the host, based on your installed version of GitLab:
 
 If you're using the [GitLab Helm chart](https://gitlab.com/gitlab-org/charts/gitlab)
 on a Kubernetes cluster, you can run the backup task by using `kubectl` to run the `backup-utility`
-script on the GitLab task runner pod. For more details, see
-[backing up a GitLab installation](https://gitlab.com/gitlab-org/charts/gitlab/blob/master/doc/backup-restore/backup.md#backing-up-a-gitlab-installation).
-
-```shell
-kubectl exec -it <gitlab task-runner pod> -- backup-utility
-```
+script on the GitLab toolbox pod. For more details, see the
+[charts backup documentation](https://docs.gitlab.com/charts/backup-restore/backup.html).
 
 Similar to the Kubernetes case, if you have scaled out your GitLab cluster to
 use multiple application servers, you should pick a designated node (that isn't