Before the workshop starts
Complete these steps on your laptop before day one, it takes about 15 minutes. If anything doesn't work, check the troubleshooting section below, and bring it to us at the start of the session rather than struggling alone.
0%
Install tools
Connect network
Trust certificate
Log in
GitHub access
Your links
1Install the CLI
You need the OpenShift command line client (
oc). Everything else runs in your browser.brew install openshift-cli
If winget isn't available on Windows
Download oc from mirror.openshift.com, unzip it, and put oc.exe in a folder that's on your PATH.
Check it worked:
oc version --client
You should see a version number. "Command not found" almost always means it isn't on your
PATH yet, close and reopen your terminal first.2Connect to the training network
Connect the VPN
Use the WireGuard config your trainers sent you. The training cluster is not on the public internet, nothing on this page will work until it's connected.
Company networks often block this
Some corporate Wi-Fi and VPN setups restrict outbound WireGuard traffic. If you can't get connected, try tethering to a personal mobile hotspot instead.
Check it's working:
ping 192.168.0.220
You should see replies coming back. If not, the VPN isn't connected or hasn't finished starting, wait a few seconds and try again. Still nothing? Check your WireGuard config's
AllowedIPs includes 192.168.0.220/32, without that route, traffic to the cluster never enters the tunnel.Add the cluster hostnames
WireGuard doesn't push DNS here, so your laptop doesn't know these names yet. Add them to your hosts file, all pointing at that same address:
sudo tee -a /etc/hosts <<'EOF' 192.168.0.220 api.okd.internal 192.168.0.220 console-openshift-console.apps.okd.internal 192.168.0.220 oauth-openshift.apps.okd.internal 192.168.0.220 learning.apps.okd.internal 192.168.0.220 argocd-server-argocd.apps.okd.internal 192.168.0.220 sso.okd.internal 192.168.0.220 console.okd.internal EOF
Windows: Notepad++ must run as Administrator
Right-click Notepad++ in the Start menu and choose Run as administrator before opening the file, otherwise Windows won't let you save changes to it.
Check it worked:
ping console-openshift-console.apps.okd.internal should reply from 192.168.0.220.3Trust our certificate authority
The workshop cluster uses certificates issued by our own internal certificate authority rather than a public one. Your laptop doesn't know about it yet, without this step you'll see security warnings on every page, and
Download root-ca.crtoc will refuse to connect entirely.Then install it:
sudo security add-trusted-cert -d -r trustRoot \ -k /Library/Keychains/System.keychain root-ca.crt
Using Firefox? There's an extra step
Chrome, Edge and Safari read the certificate store you just updated. Firefox keeps its own, go to Settings → Privacy & Security → Certificates → View Certificates → Authorities → Import, and select the same file.
4Log in
You'll get a username and password separately. Your username is the first part of your work email, for example
firstname.lastname.In the browser
Open the OpenShift console (in the links step below), choose okd-training as the login method, and sign in. The other option,
breakglass, is for trainers only, it won't work for you, and you don't need it.On the command line
This is the one that catches everybody
oc login -u username -p password does not work here, and the error it gives isn't helpful. We use single sign-on, and that login form can't handle it.Use this instead, it opens your browser, you sign in there, and the terminal picks the session up automatically:
oc login --web
Then confirm it worked:
oc whoami
You should see your username. You can also copy a ready-made login command from the console, click your name in the top right, then Copy login command.
Check you can create a project
You'll do this properly in the first lab, but it's worth confirming now that your account has the right permissions:
oc new-project test-$(whoami) oc delete project test-$(whoami)
If the first command is refused, tell your trainers before the workshop starts.
5GitHub access
The sample application you'll build from lives in two repos on GitHub. You'll need access to both before the workshop starts:
To get access:
- Accept the invite to the
mtdtechnology-netorganization ongithub.com, check your email or your GitHub notifications. - Make sure you're added to the
openshift-workshop-extGitHub team, that's what grants access to the repos above. If you don't see them after accepting the invite, tell your trainers.
Note: the certificate for the training cluster is handled separately, see the Trust our certificate authority step above. Your trainers will send that file directly; nothing to do with GitHub access.
6Your links
All of these need the VPN connected.
OpenShift consoleThe cluster's own web interface, where you'll spend most of the workshop.Learning platformCourse chapters, exercises and progress.Argo CDUsed in the GitOps chapters.KeycloakSingle sign-on for the console and the sample application.Cluster APIWhat oc login --web connects to.
Credentials handed out on the day: some exercises need tokens your trainers will give you at the start, a GitHub token for building the sample application, and a client secret for single sign-on. You don't need to arrange these yourself.
If something doesn't work
Bring problems to the first session rather than struggling alone, sorting one out takes a couple of minutes; finding it mid-exercise costs everyone time.
Still stuck after trying these? Come to the session and tell us at the start.