1. If you are no longer logged into your VDI desktop or lost the RDP session to the Tanzu Desktop, then follow the instruction in Lab 10 Task 1 (Steps 1 through 8) before continuing to step 2
2. From the Tanzu Desktop Launch Firefox, Edge or Brave
   (NOTE: You will use this browser instance to access the SDDC vCenter as CloudAdmin)
3. In the browser go to https://vmc.vmware.com/sddcs/console
4. log in as:
   • vmcexpert{1|2|3}-##@27virtual.net (where ## is your student number) i.e vmcexpert1-02@27virtual.net
   • {Password-Provided-by-Instructor}
5. In the upper right-hand corner Click the dropdown next to <your-username>
6. Confirm you are logged into the correct Organization, If not select it
   Note: Your correct Organization should be {Your-VMCEXPERT-Environment}-VCDR01 e.g. VMCEXPERT2-VCDR01

7. In the SDDC Tile, click Open vCenter
8. Click Show Credential
9. Copy the Default vCenter User Password (Store this for future use)
10. Click Open vCenter

11. Log into vCenter as:
    • User Name: Cloudadmin@vmc.local
    • Password: (Paste in the Password from step 9)
12. Once Logged into vCenter, inspect the Host & Clusters Inventory view
13. Take note of the Supervisor Cluster Control VMs  in the Mgmt-ResourcePool Resource Pool
    Also note the NameSpaces Resource Pool
14. In the Upper Left-hand corner, click the Hamburger Menu, Select Workload Management
15. Click the Supervisors tab to confirm the Supervisor Cluster exists and is in a Health state

16. Click the Namespaces tab
17. Click New Namespace
18. Expand vCenter (vcenter.sddc.xx.xx.xx.xx.vmwarevmc.com) and select Cluster-1
19. Type {Your Username} in the Name field I.E. vmcexpert3-33
20. Click Create

21. On the Namespace you just created, Click Add Permissions to restrict this Namespace to your DevOps user account
22. In the Add Permissions Dialog Choose/enter the following
    • Identity Source: 27Virtual.net
    • User/Group: {Your User Name} I.E. VMCEXPERT3-33
    • Role: Owner
23. Click OK

24. In the Storage Tile, Click Add Storage
25. In the Select Storage Policies dialog, select vSAN Default Storage Policy
26. Click OK

27. In the VM Service Tile, Click Add VM Class
28. In the Select Add VM Class dialog, select best-effort-medium, best-effort-small and best-effort-xsmall
29. Click OK

30. On the Status Tile In the vCenter Console, Click Open to open the Link to the Kubernetes Control Plane
31. Copy and store this URL (Do not include the https:// and the trailing "/").
    Note: You can store this in your lab input workbook

32. Launch the Windows Terminal, in the PowerShell window, type the following command to access your namespace

33. When Prompted for credentials:
    • Username: {enter your DevOps Username} I.E. vmcexpert3-33@27virtual.net
    • Password: {Password-Provided-by-Instructor}

1. Launch the Windows Terminal. In the PowerShell window, type the following command to access your namespace

2. When Prompted for credentials:
   • Username: {enter your DevOps Username} I.E. vmcexpert3-33@27virtual.net
   • Password: {Password-Provided-by-Instructor}

3. From your Tanzu Desktop, In windows explorer, navigate to C:\lab_files\vce\TMC
4. Locate the vmcexpert#.XX-cluster file
5. Double click the file to edit it in Visual Studio Code
6. With the File opened, review it's content. Observe the settings for StorageClass, VMClass and replicas that will be used for this cluster
7. Edit lines 6, 7, 16 & 21
   • name: {Your Student name}-cluster NOTE: the value should have no braces {}
   • Namespace: {Your student name}
   • vmClass: best-effort-xsmall
8. Save the file as {Your user name}-cluster.yml

9. In Windows terminal, change directory to c:\Lab_Files\VCE\TMC
10. list the files, to confirm your cluster manifest file created in step 7 - 8 exists
11. run the following command to create the cluster

12. Run the following login command to update the KUBECONFIG file:

13. When Prompted for credentials:
    • Username: {enter your DevOps Username} I.E. vmcexpert3-33@27virtual.net
    • Password: {Password-Provided-by-Instructor}

14. In the vSphere UI in the browser instance, switch back to "Hosts & Clusters" view  
15. Expand the Namespaces Resource Pool
16. Identify your namespace and expand it
17. identify your cluster and expand it
18. Notice the nodes (VMs) that were deployed when you created your cluster

1. The Authentication token stored in your local KUBECONFIG file expires every 10 hours. You may want to re-authenticate to the TKG Service before starting the lab to ensure you have access to the Supervisor cluster.
   Run the following login command to update the KUBECONFIG file:

2. When Prompted for credentials:
   • Username: {enter your DevOps Username} I.E. vmcexpert3-33@27virtual.net
   • Password: {Password-Provided-by-Instructor}

3. Run the following commands to create an NGINX pod and view it

4. In Windows Explorer, navigate to c:\Lab_Files\VCE\Pods
5. Open the nginx2.yaml file
6. examine the content of the file to determine what it specifies

7. In Windows terminal, change directory to c:\Lab_Files\VCE\Pods
8. List the contents of the directory to confirm the nginx2 file exists
9. Let's create the Pod and examine it by running the following commands:

10. In Windows terminal, run the following commands to deploy an Ubuntu pod with a standard output, view details of the Pod  and retrieve the standard output

11. To get the YAML of running Ubuntu Pod, run the following command:

12. Now, let's cleanup after ourselves and remove the pods we deployed. to do so run the following command:

13. In Windows Terminal run the following commands to disable PSP and deploy 3 nginx pods as part of your 1st deployment:

14. Now lets inspect the deployment and it's components with the following commands:

15. Modify the deployment and view its history and deployment details using the following commands

Let's retrieve further information about this deployment by using the following command

16. Run the following commands to inspect the version history and rollback to a previous version

17. Run the following commands to cleanup your deployment and verify the cleanup removed your deployment

1. In Windows Explorer, navigate to C:\Lab_Files\VCE\Services
2. Open the svc-manifest1.yaml file and examine its content

3. In Windows Terminal, execute the following commands to deploy the pods and service. Also, review the service deployment

4. Now, we will view the pods and delete one of them to observe what happens. Execute the following commands to do so:

5. Now let's run a container that has the curl command installed in the image. Let's use the following imperative commands to deploy a curl container and exec into a shell

Now, let's perform a cleanup before moving forward. To do so we will exit Curl, delete the service and any containers. Execute the following commands:

1. In Windows Explorer, navigate to C:\Lab_Files\VCE\Load_Balancers
2. Open the lb-manifest.yaml file and review its content

3. In Windows Terminal, execute the following command to provision and investigate the deployment:

4. From the Tanzu desktop, open a browser instance and navigate to the external IP of the Load Balancer service

5. Try out your Tetris skills
6. Delete the deployments, replica sets, pods and services by executing the following command