Agent Deployment

This guide covers common deployment patterns for the Aegis Agent.

Deployment Options

• Linux host (systemd): best for EC2/bare metal.
• Kubernetes (Helm): best for clusters; typically deployed as a DaemonSet.

Linux Host (systemd)

Recommended path:

1. Sign in to Axis.
2. Go to Environments and generate an install script for the target environment.
3. Run the script on the host.

Warning

The generated install script contains a bootstrap token. Treat it as a secret and do not commit it to source control.

Kubernetes (Helm)

In Kubernetes, agents are usually deployed as a DaemonSet.

High level steps:

1. Obtain a bootstrap token for enrollment.
2. Create a Kubernetes Secret containing the token.
3. Install/upgrade the Helm release pointing at your control plane URL.

See Quick Start for copy/paste commands.

Upgrades

• Prefer rolling upgrades (Kubernetes DaemonSet rollingUpdate or systemd restart).
• Keep bootstrap tokens single-use; do not reuse install scripts for multiple hosts.

Uninstall

• Linux: stop and disable velikey-aegis, then remove /opt/velikey-aegis (if used).
• Kubernetes: uninstall the Helm release and delete the agent secret/config.