CP/DP Split: update a few more container references (#3359)

Author: sjberman

.github/ISSUE_TEMPLATE/bug_report.md

@@ -24,8 +24,8 @@ A clear and concise description of what you expected to happen.
 * Version of Kubernetes
 * Kubernetes platform (e.g. Mini-kube or GCP)
 * Details on how you expose the NGINX Gateway Fabric Pod (e.g. Service of type LoadBalancer or port-forward)
-* Logs of NGINX container: `kubectl -n nginx-gateway logs -l app=nginx-gateway -c nginx`
-* NGINX Configuration: `kubectl -n nginx-gateway exec <gateway-pod> -c nginx -- nginx -T`
+* Logs of NGINX container: `kubectl -n <nginx-deployment-namespace> logs deployments/<nginx-deployment>`
+* NGINX Configuration: `kubectl -n <nginx-deployment-namespace> exec -it deployments/<nginx-deployment> -- nginx -T`
 
 **Additional context**
 Add any other context about the problem here. Any log files you want to share.

docs/developer/testing.md

@@ -69,19 +69,19 @@ Follow the steps below for manual testing:
    - Logs of the `nginx-gateway` container. Look out for unexpected error logs or panics.
 
      ```shell
-     kubectl -n nginx-gateway logs <ngf-pod-name> -c nginx-gateway
+     kubectl -n nginx-gateway logs <ngf-pod-name>
      ```
 
    - Logs of the `nginx` container. Look for unexpected error logs and verify the access logs are correct.
 
      ```shell
-     kubectl -n <nginx-pod-namespace> logs <nginx-pod-name> -c nginx
+     kubectl -n <nginx-pod-namespace> logs <nginx-pod-name>
      ```
 
    - The generated nginx config. Make sure it's correct.
 
      ```shell
-     kubectl exec -it -n <nginx-pod-namespace> <nginx-pod-name> -c nginx -- nginx -T
+     kubectl exec -it -n <nginx-pod-namespace> <nginx-pod-name> -- nginx -T
      ```
 
    - The statuses of the Gateway API Resources. Make sure they look correct.