Add credentials section

02-launch-vm/README.md

@@ -50,3 +50,24 @@ Instance Labels (optional): set vmName to the Name at the top
 Now click the blue "Create" button on the bottom right.
 
 CONGRATS!  You've just deployed your first Harvester VM.  Now, we wait a minute or two while kube-virt gets storage, assigns the VM to a node, and starts it.  This typically takes ~1-10 minutes.
+
+(If you see an error about a VMI hook failure, it should clear once storage has provisioned.)
+
+## Accessing the VM 
+
+Once the VM shows a status of Running (from Off, then Assigned), you can now access it through three different methods.  The Console drop down has options for Web VNC and Serial (No specialjava agents or browser plugins needed here!).  The VNC method is certainly prettier but you might get more kernel info from the serial console and the serial console can work with copy-and-paste.
+
+The other option is to ssh using the IP address that was assigned shortly after startup via DHCP.  
+
+By this point, you may have noticed that we never set credentials.  Oops, silly me.  Let's fix that now: 
+* Click on your VM's name 
+* Click on the Access Credentials on the left-hand side.  This shows the current config, but we need to *Edit* the VM to update it.  
+* Click on the three dots on the top right and select "Edit Config"
+* Click on Access Credentials again and you'll see options to add a Basic Auth or SSHKey 
+* Use Basic Auth for password access (required for VNC/console) and/or SSHKey (public) for ssh.  
+* Add user and use 'opensuse' for the user name so you'll have sudo.
+* Save when you're done
+
+Since this leverages cloud-data to do this, you'll need to reboot the VM for it to take effect:  Select "Save & Restart" or click the three dots on the right side of the VM and select Restart from there.
+
+Note that when it comes back up, your credentials should work once cloud-init is applied shortly after boot and that the IP address may have changed after restart.