diff --git a/trento/xml/article_sap_trento.xml b/trento/xml/article_sap_trento.xml
index f49b9e39..585e7c90 100644
--- a/trento/xml/article_sap_trento.xml
+++ b/trento/xml/article_sap_trento.xml
@@ -2393,6 +2393,34 @@ In the Trento dashboard, go to the overview corresponding to the object for whic
+
+
+
+ Updating Trento Checks
+ Configuration checks are an integral part of the &t.server;. The checks are delivered as a separate component of the &t.server;. This allows customers
+ to update the checks catalog in their setup whenever updates to existing checks and new checks are released, without
+ waiting for a new version release cycle.
+ The procedure of updating the configuration checks depends on the &t.server; deployment type: &k8s;, systemd or containerized.
+ In a k8s; deployment, checks are delivered as a container image and you can
+ use Helm with the following options to pull the latest one available into your setup:
+
+ helm ... \
+ --set trento-wanda.checks.image.tag=latest \
+ --set trento-wanda.checks.image.repository=registry.suse.com/trento/trento-checks \
+ --set trento-wanda.checks.image.pullPolicy=Always \
+ ...
+
+ In a systemd deployment, checks are delivered as an RPM package, and you can
+ use zypper to update your checks catalog to the latest version:
+ &prompt.user;sudo zypper ref
+&prompt.user;sudo zypper update trento-checks
+ In a containerized deployment, checks are delivered as a container image, and
+ you can user Docker to pull the latest version into the trento-checks volume that was
+ created during the installation process:
+ &prompt.user;docker run \
+ -v trento-checks:/usr/share/trento/checks \
+ registry.suse.com/trento/trento-checks:latest
+