root@acerate1:~#  kubectl get svc -n ns-team1 | awk {' print $1" " $5'} | column -t NAME PORT(S) nodejs-deployment-team1-nodejssample-nodejs 3000:31061/TCP root@acerate1:~#  kubectl get svc -n ns-team2 | awk {' print $1" " $5'} | column -t NAME PORT(S) nodejs-deployment-team2-nodejssample-nodejs 3000:30905/TCP root@acerate1:~#  kubectl exec -it nodejs-deployment-team1-nodejssample-nodejs-c856dff96-z84gv -n  ns-team1 -- /bin/bash -c "curl 10.1.219.133:3000" <!-- Licensed Materials - Property of IBM (C) Copyright IBM Corp. 2018. All Rights Reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP  Schedule Contract with IBM Corp. --> <!DOCTYPE html> <html lang="en"> <head> .... .... <div class="footer"> <p>Node.js is a trademark of Joyent, Inc. and is used with its permission. We are not  endorsed by or affiliated with Joyent.</p> </div> </div> </body> Example 6-4 Getting the service details of the pod deployed by team1 Example 6-5 Getting the service details of the pod deployed by team2 Example 6-6 Accessing the pod of team2 from the pod of team1 Example 6-7 Patching the namespace for team1 with label name: ns-team1 apiVersion: v1 kind: Namespace metadata: name: ns-team1 labels: name: ns-team1 apiVersion: v1 kind: Namespace metadata: name: ns-team2 labels: name: ns-team2 Example 6-8 Patching the namespace for team2 with label name: ns-team2 At this point, we need to create network policies to create firewall rules at the namespace  scope. This will stop the communication between pods of team1 and team2. Example 6-7,  Example 6-8, Example 6-9 on page 245, Example 6-10 on page 245, and Example 6-11 on  page 245 show how to do it.  244  IBM Cloud Private System Administrator’s Guide