Bundles Distribution

The agent uses the same distribution flow as ML model deployments. The deployed bundles are essential for two key functionalities:

  1. Dashboard: The bundles are utilized by the Dashboard to populate the Download page, enabling users to access and download the available versions.
  2. Agent: The bundles also support the AutoUpdate functionality of the agent, ensuring that it can automatically update itself to the latest version when available.

Deployment flow:
  1. Once a new bundle is deployed, the requested agent artifacts are copied into a MinIO bucket on the customer's cluster.
  2. Subsequently, the pod named static-server (an Nginx server) is restarted. Upon startup, this pod copies the artifacts from the MinIO bucket to /var/static/agent/(stable|beta).
  3. From this point, the artifacts can be accessed via the following URLs:
    1. https://{cluster}/static-server/static/agent/stable/ - for default stable deployment.
    2. https://{cluster}/static-server/static/agent/beta/ - for optional beta deployment.
Note:

The previous pods auto-update-server and synergy-server are deprecated.

Click here for runbook on Accessing the Agent buckets on MinIO.

The agent supports two types of artifact distributions:

  1. Stable: This is the default distribution method for artifacts.
  2. Beta (for agent version 4.1.0 and above): This method is for optional beta distribution. The process for deploying beta artifacts is detailed further down on this page.