UsageCloud Private — administrator training

Your lab environment

The button below builds a complete, private installation of UsageCloud Private for you to work in: the platform, its identity provider, and a terminal in your browser. Nothing to install.

The button below builds a private Kubernetes cluster for you to work in, ready for UsageCloud Private, and a terminal in your browser. You install the product yourself. Nothing to install on your own computer.

The button below builds an empty, private Kubernetes cluster for you to work in, and a terminal in your browser. You prepare the cluster yourself, then install UsageCloud Private on it. Nothing to install on your own computer.

Your environment takes about fourthree minutes to build, and it is deleted 60 minutes later. Nothing you do in the environment is saved, and that is deliberate. If you break the environment, run out of time, or come back tomorrow, start another one. Starting another is the normal way to recover from anything.

Deleted in —

How this page works

Keep this tab open. This page holds your logins, your clock and the exercises, and it is the only place your logins are written down. The toolbar above has three tabs:

Keep this tab open. This page holds your login, your clock and the exercise, and it is the only place your login is written down. The toolbar above has three tabs:

Overview	This tab: what is in your environment, and who you can sign in as.
Links	The threefour parts of your environment: the product's user interface, a terminal, the operations console, and the Keycloak console where users and roles live. Open them in new tabs from the Links tab.
Links	A terminal, where you are a cluster administrator, and your test address, which answers once Task 5 is done and becomes the product in Task 6. Open them in new tabs from the Links tab.
Exercises	Six tasks, about 30 minutes, in which you prepare an empty Kubernetes cluster for the product, then install the product on it. When you finish a task, run the '`lab check`' command in the terminal to confirm it is done. Once all six pass, '`lab check`' prints a completion word. Choose that word in the lab's quiz, back in the course.
Exercises	Four tasks, about 30 minutes. Each task starts by asking you to predict what will happen. When you finish a task, run the '`lab check`' command in the terminal to confirm the task is done. Once all four tasks pass, '`lab check`' prints a completion word. Choose that word in the lab's quiz, back in the course: the quiz you came here from.
Exercises	Two short tasks, about ten minutes, that repeat the steps from the lecture. Nothing is marked.
Exercises	Four tasks, about 40 minutes: back up an installation, upgrade it, roll it back, and bring its workflows back. When you finish a task, run the '`lab check`' command in the terminal to confirm it is done. Once all four pass, '`lab check`' prints a completion word. Choose that word in the lab's quiz, back in the course.
Exercises	Four tasks, about 30 minutes: your first on-call shift, in the operations console. When you finish a task, run the '`lab check`' command in the terminal to confirm it is done. Once all four pass, '`lab check`' prints a completion word. Choose that word in the lab's quiz, back in the course.
Exercises	Five tasks, about 30 minutes, in which you install the product yourself. When you finish a task, run the '`lab check`' command in the terminal to confirm it is done. Once all five pass, '`lab check`' prints a completion word. Choose that word in the lab's quiz, back in the course.

Keep the Role Ladder reference handy as well. The reference lists every route and the lowest role that can call it, and the predictions are easier with the reference open.

Who you can sign in as

Six logins, and every password is the username. The exercises have you move between these logins.

admin / admin signs in to every address on the Links tab, with the most access each one gives. This lab is done as Ollie, an operator. Every password is the username.

ThreeFour addresses, and none is derived from the others. Open each address in a new tab from here rather than guessing — the lab page stays open.

If a link does not answer straight away, give it another few seconds and reload.

In this lab you install the product yourself, so its address and the Keycloak console answer only after your installation is running. The terminal works from the start.

Test address — reached through a load balancer, then the front door you build

Address

Until your Gateway answers on port 443, this address shows an error from the load balancer (502 or 503). That is expected before Task 5.

After Task 6, this address is the product. Sign in as admin, with the password admin.

UsageCloud Private — the product's main user interface. Where you work as each user

Address

Every password is the username.

The password is the username.

Operations console — runs, quarantine, events, pods and logs. Most of this lab happens here

Address
Sign in	ollie / ollie
Sign in	admin / admin

Ollie holds the operator role, the one an on-call administrator works with. Sign in to the product as ollie too.

Terminal — the API, and the questions the UI has no screen for

Address
Sign in

Role Ladder reference — every route and the rung it needs

Address

the Role Ladder reference

Searchable. The exercises ask you to predict before you act — predicting the answer is the skill, not finding it afterwards.

Keycloak console — users, roles and groups. Every task uses the console

Address
Sign in

⚠ Same username and password, different account. This console admin lives in Keycloak's master realm and manages users. The platform's admin, under UsageCloud Private above, lives in the fern realm and uses the platform. Two realms, two accounts that happen to share a name.

The console opens on the master realm, and every user in this lab lives in fern. After signing in, open the realm dropdown at the top of the left-hand menu and choose fern.

Environments are deleted automatically. Nothing in an environment is backed up, and none of these environments is a place to keep anything.

Your lab environment

How this page works

Who you can sign in as

Test address — reached through a load balancer, then the front door you build

UsageCloud Private — the product's main user interface. Where you work as each user

Operations console — runs, quarantine, events, pods and logs. Most of this lab happens here

Terminal — the API, and the questions the UI has no screen for

Role Ladder reference — every route and the rung it needs

Keycloak console — users, roles and groups. Every task uses the console

Your first week as the platform's administrator

Your first environment

Install UsageCloud Private

Your first on-call shift

Upgrade, and roll back

Prepare a cluster