SeqOps Agent Update Policies

Agent update policies define how SeqOps agents receive and apply software updates. Update policies allow administrators to control when and how SeqOps agents are updated. Agent update policies help administrators maintain consistent agent versions across multiple servers.

Agent updates ensure the SeqOps Agent software remains compatible with the platform and includes the latest improvements.

Update Policy Options

• •Automatic updates — SeqOps server agents update to the latest stable version during the configured maintenance window. This is the simplest option and ensures your fleet stays current without manual intervention.
• •Manual approval — Updates are downloaded to each server automatically but will not be installed until an administrator explicitly approves them. This gives you a chance to review release notes and test before rolling out.
• •Staged rollout — Updates are deployed to a small pilot group first. After a configurable delay, and assuming no issues are flagged, the update is then promoted to the rest of your fleet. This strikes a good balance between staying current and minimizing risk.
• •Version pinning — Locks SeqOps server agents to a specific version for compatibility or compliance reasons. Pinned agents will remain on their current version until the pin is removed.

SeqOps agents update according to the update policy configured by the administrator.

When Agent Updates Occur

Agent updates may occur when:

• •A new agent version is released
• •The configured update policy allows automatic updates
• •An administrator triggers a manual update

Verify Agent Version

Administrators can verify the installed agent version by checking the server entry in the SeqOps platform dashboard. You can view the current version of each agent in the Agent Inventory table. If an agent is running an outdated version, you can trigger a manual update from the agent's detail page.

Troubleshooting Agent Updates

Common issues:

• •Agent cannot download the update — verify network connectivity to SeqOps update endpoints.
• •Network restrictions block update endpoints — confirm outbound HTTPS traffic is allowed on port 443.
• •Agent version does not update due to policy restrictions — check if version pinning is enabled.
• •SeqOps Agent service fails to restart after update — review agent logs for errors and contact support if needed.

Our Recommendation

For most production environments, we recommend using staged rollouts. They give you the safety of a controlled rollout while keeping your SeqOps server agents up to date.