Deployment Configuration¶

The Deployment tab of the Agent Configuration dialog allows you to specify the target execution environment where the agent will be deployed. BizMetry uses this information to generate a fully configured installer that can deploy the agent autonomously within a Kubernetes cluster — whether on-premises or in the cloud.

To access the Deployment tab, open the Agent Configuration dialog and select Deployment from the tab bar.

Deployment Parameters at a Glance¶

The tab presents the following configuration fields, which together define the full deployment target specification:

Architecture¶

Defines the operating system and CPU architecture of the host environment where the agent will be deployed. BizMetry uses this selection to produce an agent binary and container image that is compatible with the target runtime.

Providing Deployment Parameters¶

The checkbox "I will provide deployment parameters at deploy-time" controls when the registry and ingress configuration is supplied.

Option A — Configure now (checkbox unchecked)¶

All deployment parameters — ingress type, registry URL, project, user, and password — must be filled in through this tab before downloading the agent. The installer will use these values directly, requiring no additional input at install time. This is the recommended approach for unattended, scripted deployments where the installation must be fully self-contained.

Option B — Provide at install time (checkbox checked)¶

The remaining fields in this tab are skipped during configuration. Instead, the installer script will prompt the operator for these values interactively at the moment of installation. Use this option when registry credentials or ingress details are not available at configuration time, or when different operators handle the configuration and the installation steps separately.

Ingress Type¶

The BizMetry agent is deployed behind a Kubernetes ingress load balancer, which receives inbound traffic and distributes it across the agent Pods. The installer generates ingress manifests tailored to the selected controller type, so it is essential to choose the option that matches the ingress controller already running in your target cluster.

Load balancer topology¶

When deployed, the BizMetry agent exposes two independent load balancers within the Kubernetes cluster, each serving a distinct purpose:

External load balancer Handles bidirectional communication between the BizMetry platform and the agent. The platform uses this endpoint to push commands to the agent — such as configuration updates, restart signals, and control instructions — and to receive feedback and telemetry data in return. This load balancer must be reachable from the BizMetry platform over the network.

Internal load balancer Handles inbound instrumentation data from business applications running within the same private network. Applications and/or remote clients (i.e. for data sensing topology) deliver metrics to the agent either through the BizMetry plugin deployed in the API Gateway, or directly via the BizMetry SDK. This load balancer is exposed exclusively within the internal network and is not accessible from outside it.

The ingress type selected below applies to both load balancers. Both are provisioned using the same ingress controller, so it is critical that the selected type matches the controller actually running in the target cluster.

BizMetry supports the following ingress controllers:

Registry Configuration¶

Once downloaded, the agent image must be pushed to a container image registry accessible from the target Kubernetes cluster. The fields below define the registry connection and credentials that the installer will use to perform this push.

Registry URL¶

The HTTPS URL of the container image registry associated with the target environment. This is the endpoint the installer connects to when pushing the agent image.

Project Name¶

The name of the project — or repository namespace — within the registry where the installer will push the agent image. This must be an existing project that is accessible to the configured registry user.

User Name¶

The username used to authenticate against the registry. This account must exist in the registry and must have sufficient permissions to push images to the configured project.

Password¶

The password for the registry user account specified above. Ensure that the credentials provided are correct and current, as an authentication failure will prevent the installer from pushing the agent image and will halt the deployment.

Summary¶

Related Topics¶

• Bizmetry Deployment topologies
• General Configuration
• Security Configuration
• Logging Configuration
• SLA Configuration
• Downloading and Deploying an Agent
• Restarting an Agent