In Part I of this series, we explored how to deploy the VEBA appliance. In Part II, we look at setting up a Windows workstation with the prereqs for interacting with VEBA using the Knative event processor
I first installed Visual Studio Code, a free open source code editor with wide community adoption. The installation is a simple next-next-finish. VS Code is not a requirement – any editor can be used.
We need 3 tools to deploy Knative functions to VEBA
I am not a Mac person, but you can avoid the manual installation of software by using Homebrew. The Mac commands should be:
brew install git brew install docker brew install kubernetes-cli
On Windows, if you want to avoid manual installations, install Chocolatey. The Windows install commands are:
choco install git choco install docker-desktop choco install kubernetes-cli
Screenshots of manual installation are below.
Sstart with the git download page.
I leave the defaults here
This seems to be an OK option – I’m not sure what people typically use. Through the sample code deployment I was only calling git from the Git Bash anyway, so I guess it doesn’t make a difference.
I leave all these default.
First we sign up for a Docker account
Now we download and install Docker Desktop. The installation is simple, you can find the official installation documentation here.
After installation there’s a little whale icon in my system tray
I right-click and log in with the account I just created
Now when I right-click the whale, it shows that I’m signed in.
You can get Kubectl from here. Download it to your machine, ensure the path to the location where you put the binary is in your PATH.
Now we need to copy the Kubernetes config file to our laptop so we can administer it remotely. If you did not enable sshd when you deployed the appliance, connect to the console through vCenter and issue the command:
systemctl start sshd
I use WinSCP to copy files from the appliance over SSH.
NOTE: Make sure to enable hidden files and folders in Options>Preferences>Panels
Create a folder on your local system called .kube – that’s kube with a period in front of it – in your user directory. On Windows, I create .kube in my home folder $env:USERPROFILE. On Linux/Mac, you would create $HOME/.kube
Change to /root/.kube on the VEBA appliance. Copy ‘config’ from VEBA to your local system.
On Linux/Mac, you would use the built-in SCP command
pkremer@pkremer-z01:~/.kube$ scp email@example.com:/root/.kube/config /home/pkremer/.kube The authenticity of host '10.216.146.11 (10.216.146.11)' can't be established. ECDSA key fingerprint is SHA256:I1qRx+Gf4iJb7mBKWHizl0JAMz0KhwezOrOZlFSYTg4. Are you sure you want to continue connecting (yes/no/[fingerprint])? yes Warning: Permanently added '10.216.146.11' (ECDSA) to the list of known hosts. Password: config
You should now be able to run kubectl commands against the VEBA appliance from your remote machine.
kubectl get pods -A
Don’t forget to disable sshd
systemctl stop sshd
We have now installed all of the prereqs for running our first sample function. In Part III, we will look deploy our first Knative function.