Images and License¶
License Management¶
Activating Your License¶
Upon purchasing from Juno, you will receive a license key via email from our team. This key is passed in during the Genesis deployment process to validate your subscription and activate all licensed services. You can also update your license at any time via the Genesis web UI, under the "Licensing" tab.
If you haven't received your license key or need assistance, please contact our sales team at sales@juno-innovations.com. We aim to respond to all inquiries within one business day.
Community Edition¶
We provide a Community Edition to enable you to evaluate, as well to support open-source developers that contribute to Helios, our containarized workstation platform.
The Community Edition enables you to run up to 5 workstations for free, indefinitely and without any other restrictions on workstation functionality.
Licensing - user & workstation allowance¶
If your license is issued for a set amount of users, each user is allowed to spawn as many workstations as they wish. This means you can have up to 20 unique users spawn multiple machines each. The license cap counts unique users across all your workstations.
There is no limit on the amount of users allowed to log into the platform. Only users with active workstations count against the allowance.
For workstation-bound licenses, the amount of users is not considered and only the amount of running workstations is evaluated.
Image Access¶
DockerHub Availability
Juno container images are publicly available on DockerHub for direct access. You can pull images directly from our DockerHub repository without any special requests or approval process. To launch Genesis, you will need to provide the license key during the deployment process.
Air-Gapped Environments
If you are deploying in an air-gapped environment, you will need to follow the manual image deployment steps below to download and load images into your private registry.
Below you can find that you will need to ingest for an airgapped deployment.
It tracks latest releases of our charts:
The deployment also leverages a few upstream components:
- Nvidia GPU-Operator - v24.9.0
- ArgoCD - v3.0.9
- ingress-nginx - v4.12.1
If your cluster has those pre-deployed or if you prefer to manage those yourself, it is likely they will work out of the box. The above versions are what we actively test our airgapped deployment against and what we recommend - they are not technically a hard requirement.
The images you will need to get running with the above versions are:
| Image Name | Component |
|---|---|
| docker.io/junoinnovations/genesis:v1.1.1` | Juno Genesis |
| docker.io/junoinnovations/titan:v1.0.1` | Juno Genesis |
| docker.io/junoinnovations/terra:v1.0.1` | Juno Genesis |
| docker.io/junoinnovations/hubble:v1.1.0` | Juno Orion |
| docker.io/junoinnovations/kuiper:v1.0.1` | Juno Orion |
| nvcr.io/nvidia/cuda:12.6.3-base-ubi9 | GPU-Operator |
| nvcr.io/nvidia/cloud-native/dcgm:3.3.9-1-ubuntu22.04 | GPU-Operator |
| nvcr.io/nvidia/cloud-native/k8s-mig-manager:v0.10.0-ubuntu20.04 | GPU-Operator |
| nvcr.io/nvidia/cloud-native/k8s-kata-manager:v0.2.2 | GPU-Operator |
| nvcr.io/nvidia/cloud-native/nvidia-fs:2.20.5 | GPU-Operator |
| nvcr.io/nvidia/cloud-native/gdrdrv:v2.4.1-2 | GPU-Operator |
| nvcr.io/nvidia/cloud-native/gpu-operator-validator:v24.9.0 | GPU-Operator |
| nvcr.io/nvidia/cloud-native/k8s-driver-manager:v0.7.0 | GPU-Operator |
| nvcr.io/nvidia/cloud-native/vgpu-device-manager:v0.2.8 | GPU-Operator |
| nvcr.io/nvidia/driver:550.127.08 | GPU-Operator |
| nvcr.io/nvidia/gpu-operator:v24.9.0 | GPU-Operator |
| nvcr.io/nvidia/k8s-device-plugin:v0.17.0 | GPU-Operator |
| nvcr.io/nvidia/kubevirt-gpu-device-plugin:v1.2.10 | GPU-Operator |
| nvcr.io/nvidia/k8s/dcgm-exporter:3.3.9-3.6.1-ubuntu22.04 | GPU-Operator |
| nvcr.io/nvidia/k8s/container-toolkit:v1.17.3-ubuntu20.04 | GPU-Operator |
| registry.k8s.io/nfd/node-feature-discovery:v0.16.6 | GPU-Operator |
| registry.k8s.io/ingress-nginx/controller:v1.12.1 | ingress-nginx |
| registry.k8s.io/ingress-nginx/kube-webhook-certgen:v1.5.2 | ingress-nginx |
| quay.io/argoproj/argocd:v3.0.9 | ArgoCD |
| ghcr.io/dexidp/dex:v2.41.1 | ArgoCD |
| docker.io/library/redis:7.2.7-alpine | ArgoCD |
When using our workstation images, we recommend you pull the latest stable tag of Polaris or Helios (currently in beta!). The workstation image is not included in the list below, since there are multiple choices - we ship multiple distros and flavors that serve different industry-specific use cases.