The blacklist is a soft deny mechanism that prevents Artica software packages from being pushed to a specific agent node, while leaving all monitoring, operational, and binary upgrade capabilities intact.
In this scenario, the administrator can trigger bulk updates without the risk of automatically updating a critical component that would require more advanced testing before deployment.
They may also choose to perform updates manually on specific machines when greater control is required.
This is typically the case when you operate, for example, both a validation (staging) platform and a production platform, where the production environment cannot be updated arbitrarily or without strict change management procedures.
A blacklisted node continues to:
A blacklisted node will not receive:
apt-get upgrade)apt-get updateUse the blacklist to freeze the software state of a node — for example, to hold a known-good version while an issue is investigated, or to exclude a node from a fleet-wide rollout.
On the Agents List table, select the Agent you need to deny from updates.



In scenarios where you operate both a validation (staging) platform and a production platform with multiple servers, it is more efficient to manage updates at the group level rather than handling each agent individually.

