Skip to main content

Install G8 itself

G8 is the second half of the installation: one server that serves the console and the API, on a PostgreSQL database you provide. It is installed on OKD or OpenShift with its Helm chart. A release also ships an offline bundle, but that bundle is a rehearsal that proves the images start on an air-gapped machine, not an installation; an installation on a Docker host is not offered yet. This session says what the server needs before it starts, what it prints once it does, and hands you to the page that holds the procedure.

Before this session​

  • A gateway cluster is running and you hold its Admin API address and admin key, from Plan the installation.
  • A PostgreSQL database for G8, reachable from the cluster, and a person who can create its role and database.

In this session​

  1. Have ready what the server reads at start: the database connection, the key that seals stored passwords and admin keys, the gateway's Admin API and the host name of the console. Install G8 on OKD or OpenShift lists them, and Server configuration explains every setting.
  2. Follow the procedure on Install G8 on OKD or OpenShift: the namespace, the three Secrets, the values file, the install, and the checks through the Route.
  3. Check the server from outside the cluster. Its health address answers as soon as it listens; its readiness address answers once the database and the sealing key check out. What to watch explains all three addresses.
  4. Find the setup token in the server's log. Printed in the server log while g8 has no users. You use it in the next session to create the first administrator.

What you should see​

The console opens in a browser at the host name you chose and asks for the setup token, because no user exists yet. The readiness address answers that the server is ready. The first environment exists already, created at the first start from the slug, the Admin API address and the admin key the server was given; the next session opens it, sets the address your clients call and checks the connection.

Where this leads​

First sign-in and the first environment creates the first administrator with the setup token and connects the first environment to the cluster. The day-to-day of the server, backups, the sealing key, upgrades and what to watch, is under Run the server in Operate.

G8 dev