Step 1 sets up your Kubernetes environment. Any container runtime software (a software component that can run containers on a host operating system), such as Docker, can also be used to run Hopr sidecars, but if you are using a different containerized system, then the details of setting up your containerized system will be different from the specifics described for Kubernetes below.

Kubernetes Cluster

In order to get up and running, you will need access to a Kubernetes (K8s) cluster in your environment. If you do not already have a Kubernetes cluster up and running in your environment, a cluster can be created using a lightweight Kubernetes installation, such as K3s or minikube, to house Hopr's sidecars alongside your workloads.

Hopr License

When registering with Hopr you will receive a Hopr license file. This license will grant you access to features and functionalities, and is needed in order to successfully setup Hopr in your environment. The license file (.lic) will look like the following:

Key: 46O0IJNIM9VPQk4Be7hO72S4mUCdI9B6JmjbD0m4Vv0=
License with expiry 2022-10-08T23:59:59.999999 created at: hopr.lic

WwIWOuohjcSlXFjaG+TcCOuk7AXxlM8xaM3r5eTubnnVN+bY2m2DB87CieiTEhhtZ6lKszmoP0GDiwYOVtlpsx1KiuTn1Q16ZODBgWzXFiOpQVNSgQrO938LKzORaoPxTLEk

Hopr Repo

When registering with Hopr you will also receive access to the Hopr Container Repository in the form of a Docker configuration file (config.json). The Hopr repo is a private repository for XTRA's container that can be pulled and deployed to your Kubernetes cluster. In order to be able to pull from our repo you'll need your config.json.

Important! This file will be used for both direct access via Docker pull and a kubernetes secret. The config.json file contains plaintext user and password information. As such, IT IS EXTREMELY IMPORTANT THAT THIS FILE BE PROTECTED!

{
  "auths": {
    "repo.hoprapi.com": {
      "username": "nick",
      "password": "hoprXTRA12345",
      "email": "dev@hopr.co",
      "auth": "bmljazpob3ByWFRSQTEyMzQ1"
    }
  }
}

‍