**************** TEAM0 **************** team00 optools URL: https://9.56.28.25:30003 team00 proxy URL: https://9.56.28.25:30004 team00 USERNAME: siler23@ibm.com team00 PASSWORD: team00pw2266 Full Cleanup Command: TEAM_NUMBER=1 PREFIX=ibp-auto-deploy  ./cleanupNamespaces.sh List of ports for each team for quick reference cat portList.txt You use these details to log in and initialize the console as described in 4.2.2, “Initializing  blockchain console for other users” on page 167. If the script times out instead of reaching this message, follow the steps in the “Verifying the  console with Kubectl (command line)” section. If that verification fails, seek further help in  section 4.5, “Troubleshooting the installation” on page 194. Verifying the console with Kubectl (command line) Perform the following steps: 1. Choose one of the options to set up kubectl to point to the namespace for your blockchain  console. (Choose only one of the two options.)  Kubectl option Details cloudctl Use cloudctl to log in to the namespace that you installed the blockchain console helm release into.  This action generates two results: GLYPH<SM590000> Configures kubectl with a new authentication token for the Kubernetes API server. GLYPH<SM590000> Sets kubectl to point to the correct namespaces for commands. You don’t need to use the  -n  namespace  (the alternative) flag.  The syntax is as follows: cloudctl login -a https://< cluster_hostname >:8443 --skip-ssl-validation -n  < blockchain_console_namespace > Example 4-12 shows a sample  cloudctl  login. kubectl config Set the namespace of a previously authenticated user to the namespace of the blockchain console  helm release by using the kubectl config command. (Previous authentication would have been  done through cloudctl or a kubectl token that was received from the IBM Cloud Private UI.) kubectl config set-context --current --namespace=< blockchain-console-namespace > Example 4-13 on page 154 shows a sample command for setting the namespace for  kubectl  config . Example 4-12 Sample cloudctl login  cloudctl login -a https://mycluster.icp:8443 --skip-ssl-validation -n  ibp-auto-deploy-team00 Username> admin Password>  Authenticating... OK Targeted account mycluster Account (id-mycluster-account) Chapter 4. IBM Blockchain Platform installation and configuration  153