Updated asset paths and next config for cname.
This commit is contained in:
@ -18,7 +18,7 @@ You're in a race to reach the highest score before the session concludes! If mul
|
||||
## 1.1 - The hackathon scenario
|
||||
|
||||
<Zoom>
|
||||
| |
|
||||
| |
|
||||
|:-----------------------------------------------------------------------------:|
|
||||
| *Acme Financial Services* |
|
||||
</Zoom>
|
||||
@ -39,7 +39,7 @@ All challenge tasks must be performed on this cluster so your solutions can be g
|
||||
You can and are encouraged to use any supporting documentation or other resources in order to tackle each of the challenge tasks.
|
||||
|
||||
<Zoom>
|
||||
| |
|
||||
| |
|
||||
|:-----------------------------------------------------------------------------:|
|
||||
| *OpenShift bare metal cluster console* |
|
||||
</Zoom>
|
||||
@ -54,7 +54,7 @@ To get underway open your web browser and navigate to this link to allocate an e
|
||||
Register for an environment using `[team name]@redhat.com` and the password provided by your hackathon organisers. Registering with a team email will mean all your team members will be able to see the same cluster details for your shared team cluster.
|
||||
|
||||
<Zoom>
|
||||
| |
|
||||
| |
|
||||
|:-----------------------------------------------------------------------------:|
|
||||
| *Hackathon team registration page* |
|
||||
</Zoom>
|
||||
|
||||
@ -30,7 +30,7 @@ Documentation you may find helpful is:
|
||||
For this challenge you will know you are successful and will be awarded points when your virtual machine boots the given iso and shows the following logo in vnc console:
|
||||
|
||||
<Zoom>
|
||||
| |
|
||||
| |
|
||||
|:-----------------------------------------------------------------------------:|
|
||||
| *Crusty corp financial appliance boot screen.* |
|
||||
</Zoom>
|
||||
|
||||
@ -15,7 +15,7 @@ You know KVM & KubeVirt has supported a similar feature called "Live Migration"
|
||||
The Acme Financial Services team have put you on the spot, can you pull off a virtual machine live migration? 😅
|
||||
|
||||
<Zoom>
|
||||
| |
|
||||
| |
|
||||
|:-----------------------------------------------------------------------------:|
|
||||
| *He's dead Jim...* |
|
||||
</Zoom>
|
||||
|
||||
@ -19,7 +19,7 @@ The Acme team are stuck on how they might implement this goal within their curre
|
||||
Your local pre-sales team has offered to setup an example environment for Acme and step through how to enable the feature. No worries right. After all, how hard can it be?
|
||||
|
||||
<Zoom>
|
||||
| |
|
||||
| |
|
||||
|:-----------------------------------------------------------------------------:|
|
||||
| *"We've all said it 😂"* |
|
||||
</Zoom>
|
||||
|
||||
@ -15,7 +15,7 @@ The Acme team have talked about modernisation throughout the proof of concept so
|
||||
This is it. No pressure but we need to nail this!
|
||||
|
||||
<Zoom>
|
||||
| |
|
||||
| |
|
||||
|:-----------------------------------------------------------------------------:|
|
||||
| *"The best of both worlds!"* |
|
||||
</Zoom>
|
||||
@ -41,7 +41,7 @@ Once the workloads are deployed your challenge is to create one service named `a
|
||||
You'll know if this is working correctly when you can see two pods appearing in your service pod listing:
|
||||
|
||||
<Zoom>
|
||||
| |
|
||||
| |
|
||||
|:-----------------------------------------------------------------------------:|
|
||||
| *"One service balancing traffic across a vm and standard pod!"* |
|
||||
</Zoom>
|
||||
|
||||
Reference in New Issue
Block a user