diff --git a/doc/backup-restore/backup.md b/doc/backup-restore/backup.md
index 0b60d6942ea3dd325b40e52a3a338c90df329f80..750ee54f0cb4893bf9f7273b54ec5f402e6d8b6b 100644
--- a/doc/backup-restore/backup.md
+++ b/doc/backup-restore/backup.md
@@ -12,7 +12,7 @@ Follow these steps for backing up a GitLab Helm chart based installation
 1. Ensure the task runner pod is running, by executing the following command
 
     ```
-    $ kubectl get pods --all-namespaces | grep task-runner
+    $ kubectl get pods -lrelease=RELEASE_NAME,app=task-runner
     ```
 1. Run the backup utility
     ```
diff --git a/doc/backup-restore/restore.md b/doc/backup-restore/restore.md
index db62b346bd507cb8655d1b8a01a45606a5347cb5..6e063241eedd256b175d94037482f40711559c52 100644
--- a/doc/backup-restore/restore.md
+++ b/doc/backup-restore/restore.md
@@ -19,7 +19,11 @@ The backup utility provided by GitLab Helm chart supports restoring a tarball fr
 
 The steps for restoring a GitLab installation are
 
-1. Make sure you have a running GitLab instance by deploying the charts. Ensure the `task-runner` pod is enabled and running.
+1. Make sure you have a running GitLab instance by deploying the charts. Ensure the `task-runner` pod is enabled and running by executing the following command
+
+    ```
+    $ kubectl get pods -lrelease=RELEASE_NAME,app=task-runner
+    ```
 1. Get the tarball ready in any of the above locations. Make sure it is named in the `<timestamp>_<version>_gitlab_backup.tar` format.
 1. Run the backup utility to restore the tarball