How to install Hyperglance on your own Instance or VM
If you need to install Hyperglance on your own hardened/golden VM, follow these instructions
The Hyperglance installer uses the Hyperglance CLI to install on your remote instance.
The installer has been tested against:
- Amazon Linux 2023
- Alma Linux 9
- RHEL (Red Hat Enterprise Linux) 9
- Rocky Linux 9
- Ubuntu 22.04 (LTS) & Ubuntu 24.04 (LTS)
General Pre-Requisites (Local)
- Docker Installed and Running on your LOCAL system. We ship updates to the Hyperglance cli via docker containers and docker hub.
- SSH access to the deployment target to upload the installer and associated tooling. If using the
hg install remotecommand, you will also need the SSH private key and user that has root permissions.
General Pre-Requisites (Remote / Deployment Target)
- The Hyperglance CLI will require access to the internet. The installer reaches out to a number of locations to acquire all the components for both the Kubernetes runtime (RKE2) as well as any pre-requisites.
Deployment instructions
Install Remotely To Host
- Pull and run the latest Hyperglance CLI container. Replace
PATH_TO_SSH_KEYwith the correct path to the ssh you will use to connect to the remote instance.
This will place you in the containers bash shell.docker run --rm -it --pull always -v PATH_TO_SSH_KEY:/app/key.pem hyperglance/updatetool:latest
- [Optional] Test connectivity and provided user credentials against the remote host.
ReplaceSERVER_IP,YOUR_USERNAMEandSSH_PORTwith the correct values. The --key can remain as-is as we mapped it to this in the previous command.
Example usage and successful connection is shown below:hg install remote --address SERVER_IP --username YOUR_USERNAME --port SSH_PORT --key key.pem --test
root@47aeb54424fb:/app# hg install remote --address 44.201.49.121 --username ubuntu --port 22 --key key.pem --test
The authenticity of host '44.201.49.121 (44.201.49.121)' can't be established.
ED25519 key fingerprint is SHA256:unsW4k+ROzCHbpg/YRimFr1DjgZ4UufRAkGJhaVhbkg.
This key is not known by any other names
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
[INFO] Connectivity and permissions test passed! - Run the installation.
ReplaceSERVER_IP,YOUR_USERNAMEandSSH_PORTwith the correct values. The --key can remain as-is as we mapped it to this in the previous command.hg install remote --address SERVER_IP --username YOUR_USERNAME --port SSH_PORT --key key.pem --confirm
- A successful run will show
[INFO]
_____ _ _ _____ _____ ______ _____ _____ _
/ ____| | | |/ ____/ ____| ____|/ ____/ ____| |
| (___ | | | | | | | | |__ | (___| (___ | |
\___ \| | | | | | | | __| \___ \\___ \| |
____) | |__| | |___| |____| |____ ____) |___) |_|
|_____/ \____/ \_____\_____|______|_____/_____/(_)
Please wait while the remote instance is rebooted.
Install Directly On Remote Host
- Pull the latest Hyperglance CLI container, and extract the CLI and related tooling.
This will extract:
docker create --name hg_cli hyperglance/updatetool:latest && \
docker cp hg_cli:/app/. ./ && \
docker rm hg_cli && \
rm ./upgrade.sh- hg
- hg-cli-updater
- hg-cli-log-viewer
- ansible-playbook.pyz
- Upload these files to your own vm and place them under the
/usr/local/bindirectory. - Ensure these are all executable:
sudo chmod +x /usr/local/bin/hg /usr/local/bin/hg-cli-updater /usr/local/bin/hg-cli-log-viewer /usr/local/bin/ansible-playbook.pyz
- Start the installation:
sudo /usr/local/bin/hg install local --accept
- A Successful run will show:
[INFO]
_____ _ _ _____ _____ ______ _____ _____ _
/ ____| | | |/ ____/ ____| ____|/ ____/ ____| |
| (___ | | | | | | | | |__ | (___| (___ | |
\___ \| | | | | | | | __| \___ \\___ \| |
____) | |__| | |___| |____| |____ ____) |___) |_|
|_____/ \____/ \_____\_____|______|_____/_____/(_)
Please reboot to finalise the installation. - Reboot
sudo reboot now
DONE! Hyperglance should now be available using the IP / DNS Name of the host.
Apply the Hyperglance licence: https://support.hyperglance.com/knowledge/how-to-apply-a-new-license.