added note for secret to be in same namespace as workloads

secret is used to have authenticate with the private Container registry
it should be in the same namespace which container the workloads

Signed-off-by: Dipankar Das <[email protected]>

Author: Dipankar Das

content/en/docs/tasks/configure-pod-container/pull-image-private-registry.md

@@ -211,7 +211,9 @@ kubectl get pod private-reg
 ```
 
 {{< note >}}
-In case the Pod fails to start with the status `ImagePullBackOff`, view the Pod events:
+Please ensure that the Pod or Deployment, and so on, created within a particular namespace contains the necessary secret in that same namespace.
+
+Also, in case the Pod fails to start with the status `ImagePullBackOff`, view the Pod events:
 ```shell
 kubectl describe pod private-reg
 ```
@@ -242,4 +244,4 @@ Events:
 * Learn more about [using a private registry](/docs/concepts/containers/images/#using-a-private-registry).
 * Learn more about [adding image pull secrets to a service account](/docs/tasks/configure-pod-container/configure-service-account/#add-imagepullsecrets-to-a-service-account).
 * See [kubectl create secret docker-registry](/docs/reference/generated/kubectl/kubectl-commands/#-em-secret-docker-registry-em-).
-* See the `imagePullSecrets` field within the [container definitions](/docs/reference/kubernetes-api/workload-resources/pod-v1/#containers) of a Pod
+* See the `imagePullSecrets` field within the [container definitions](/docs/reference/kubernetes-api/workload-resources/pod-v1/#containers) of a Pod