prodfiler-documentation

Upgrading Prodfiler host-agent

The upgrade process varies highly depending on the type of installation.

The Prodfiler UI project menu Project > Instructions contains the project-specific data that may be needed to perform an upgrade.

Instructions menu

Find below a list of upgrade instructions for each supported platform.

Binary installation

Use the commands provided in the UI in the Instructions menu, switching the Binary tab.

Docker container

Use the commands provided in the UI in the Instructions menu, switching to the Docker tab.

OS package in .deb format

Use the commands provided in the UI in the Instructions menu, switching to the DEB Package tab.

OS package in .rpm format

Kubernetes

If you installed via Helm following the instructions in the UI, without any customizations to namespace or release name, you can upgrade with:

PRODFILER_VERSION=$(curl -s https://documentation.prodfiler.com/latest-release.md)
helm -n prodfiler upgrade pf-host-agent --set version=${PRODFILER_VERSION} \
  --set "collectionAgentHostPort=data-v2.run.prodfiler.com:443"

If you did apply different settings for your environment, verify them first and then set the new version and collectionAgentHostPort Helm values.

ECS

Depending on how you manage ECS tasks, you should upgrade the container image tag of the host-agent. You can do so via the ECS console in the browser, the AWS CLI or any other tool that keeps track of your configuration changes.

In general, these steps are required to upgrade the DAEMON task

Nomad

You should perform a rolling update of the host-agent job. Note that the update configuration is not included in the job provided by the UI, so you’ll have to amend it.

If you followed the instructions from the UI to install Prodfiler host-agent, you can get an up-to-date prodfiler.nomad job definition using the commands from the UI, then: