From fbf9a18c1758e6b73ae725e564129aef701b1cce Mon Sep 17 00:00:00 2001 From: Alberto Bravo Date: Tue, 8 Aug 2023 12:05:10 +0200 Subject: [PATCH 01/21] General improvements to installation and update procedures. --- trento/xml/article_sap_trento.xml | 80 ++++++++++++++++++------------- 1 file changed, 46 insertions(+), 34 deletions(-) diff --git a/trento/xml/article_sap_trento.xml b/trento/xml/article_sap_trento.xml index 09c3295d..7b7632e1 100644 --- a/trento/xml/article_sap_trento.xml +++ b/trento/xml/article_sap_trento.xml @@ -175,21 +175,22 @@ As agreed on https://confluence.suse.com/x/DAEcN on our Trento doc kick off - If you already use a CNCF-certified &k8s;, + If you already use a CNCF-certified &k8s; cluster, you can run the &t.server; in it. - If you have no &k8s; and want enterprise + If you have no &k8s; cluster and want enterprise support, &suse; recommends &suse; Rancher with &rancher.k8s.engine; (RKE) version 1 or 2. - If you do not have &k8s; enterprise solution and you would - like to test Trento, an easy option could be &suse;'s K3s - project which provides a single node &k8s; cluster. Note, this - is not a recommended solution for a stable Trento production, - but a viable way to get started. + If you do not have a &k8s; enterprise solution and you would + like to test Trento, &suse; Rancher's K3s could be an easy + way to get started. But beware that K3s default installation process + ]deploys a single node &k8s; cluster, which is not a recommended + setup for a stable Trento production instance. + @@ -215,9 +216,7 @@ As agreed on https://confluence.suse.com/x/DAEcN on our Trento doc kick off While the &t.server; supports various usage scenarios, depending on the existing infrastructure, it is designed to be - cloud native and OS agnostic. As such, the default installation - method provisions a minimal, single node, K3S &k8s; cluster for - running its components in Linux containers. The &t.server; can + cloud native and OS agnostic. It can be installed on the following services:
Updating &t.server; - To update the &t.server;, do the following: - - - Ensure the &t.server; is running. - - - - Ensure that credentials for &kube; are set up correctly. - For example, if you installed K3s, export the KUBECONFIG - environment variable for the same user that performed the - installation: - - export KUBECONFIG=/etc/rancher/k3s/k3s.yaml - - - - With the same user, start the update of the &t.server; running the following command: - - HELM_EXPERIMENTAL_OCI=1 helm upgrade \ + The procedure to update &t.server; depends on how it was installed. + If it was installed manually, then it must be updated manually using the latest versions + of the container images available in SUSE public registry. If was installed using the + Helm chart, it can be updated using the same Helm command as for the installation: + helm upgrade \ --install trento-server oci://registry.suse.com/trento/trento-server \ - --set trento-web.adminUser.password=ADMIN_PASSWORD \ - --set rabbitmq.auth.erlangCookie=$(openssl rand -hex 16) + --set trento-web.adminUser.password=ADMIN_PASSWORD - - Note that the experimental flag is not needed as of Helm version 3.8.0. - - - If email alerting is enabled in the environment, then the update command - should include the corresponding options: - - HELM_EXPERIMENTAL_OCI=1 helm upgrade \ + A few things to consider: + + + Remember to add set the helm experimental flag if you are using a version of Helm lower than 3.8.0. + + + + When updating from a Trento version lower than 2.0.0 to version 2.0.0 or higher, an additional parameter + must be set in the Helm command. This is a workaround for an existing bug for which we are currently working + on a fix: + helm upgrade \ --install trento-server oci://registry.suse.com/trento/trento-server \ --set trento-web.adminUser.password=ADMIN_PASSWORD \ - --set rabbitmq.auth.erlangCookie=$(openssl rand -hex 16) \ - --set trento-web.alerting.enabled=true \ - --set trento-web.alerting.smtpServer=SMTP_SERVER \ - --set trento-web.alerting.smtpPort=SMTP_PORT \ - --set trento-web.alerting.smtpUser=SMTP_USER \ - --set trento-web.alerting.smtpPassword=SMTP_PASSWORD \ - --set trento-web.alerting.recipient=ALERTING_RECIPIENT - - - Watch the &t.server; processes until they are all in ready/running status: - watch kubectl get pods - - - Open the &t.web; URL - http://TRENTO_SERVER_HOSTNAME. - - - - To check the new version, hover the mouse pointer over - the info button in the lower-left corner. - - + --set rabbitmq.auth.erlangCookie=$(openssl rand -hex 16) + + + + If email alerting has been enabled, then the corresponding trento-web.alerting parameters + should be set in the Helm command as well. + + +
@@ -2154,7 +2129,7 @@ In the Trento dashboard, go to the overview corresponding to the object for whic - Install the package: + Install the new package: &prompt.user;sudo zypper ref &prompt.user;sudo zypper install trento-agent @@ -2185,9 +2160,9 @@ In the Trento dashboard, go to the overview corresponding to the object for whic - Restart the &t.agent;: + Start the &t.agent;: - &prompt.user;sudo systemctl restart trento-agent + &prompt.user;sudo systemctl start trento-agent Check the status of the &t.agent;: @@ -2204,7 +2179,7 @@ In the Trento dashboard, go to the overview corresponding to the object for whic [...] - Check the version on the &t.web; (URL + Check the version in the Hosts overview of the &t.web; (URL http://TRENTO_SERVER_HOSTNAME). @@ -2216,23 +2191,9 @@ In the Trento dashboard, go to the overview corresponding to the object for whic
Uninstalling &t.server; - To uninstall &t.server;, perform the following steps: - - - - Ensure that credentials for &kube; are set up correctly. - For example, if you installed K3s, set the KUBECONFIG - environment variable for the user that performed the installation: - - export KUBECONFIG=/etc/rancher/k3s/k3s.yaml - - - - With the same user, run the following command: - - helm uninstall trento-server - - + If &t.server; was deployed manually, then you need to uninstall it manually. + If &t.server; was deployed using the helm chart, then w can use Helm to uninstall it as follows: + helm uninstall trento-server
From ed4847e8b15d9ed256cc3416b68a04c9a0f57c0b Mon Sep 17 00:00:00 2001 From: Alberto Bravo Date: Tue, 8 Aug 2023 13:15:16 +0200 Subject: [PATCH 03/21] Update article_sap_trento.xml --- trento/xml/article_sap_trento.xml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/trento/xml/article_sap_trento.xml b/trento/xml/article_sap_trento.xml index 4bd606f6..0e584bd6 100644 --- a/trento/xml/article_sap_trento.xml +++ b/trento/xml/article_sap_trento.xml @@ -188,7 +188,7 @@ As agreed on https://confluence.suse.com/x/DAEcN on our Trento doc kick off If you do not have a &k8s; enterprise solution and you would like to test Trento, &suse; Rancher's K3s could be an easy way to get started. But beware that K3s default installation process - ]deploys a single node &k8s; cluster, which is not a recommended + deploys a single node &k8s; cluster, which is not a recommended setup for a stable Trento production instance. @@ -234,9 +234,9 @@ As agreed on https://confluence.suse.com/x/DAEcN on our Trento doc kick off A proper, production ready installation of Trento Server requires &k8s; - knowledge. The Helm chart is meant to be used by customers lacking such knowledge, - but it delivers a basic deployment of the &t.server; with all the components running - on a single node of the cluster. + knowledge. The Helm chart is meant to be used by customers lacking such knowledge + or wanting a quick start, but it delivers a basic deployment of the &t.server; with all the components running + on a single node of the cluster.
&t.agent; requirements From 5f27d1fe2fb4098e5b9d184171c93d684ed376f9 Mon Sep 17 00:00:00 2001 From: Alberto Bravo Date: Wed, 9 Aug 2023 13:15:58 +0200 Subject: [PATCH 04/21] Update trento/xml/article_sap_trento.xml Co-authored-by: Tom Schraitle --- trento/xml/article_sap_trento.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/trento/xml/article_sap_trento.xml b/trento/xml/article_sap_trento.xml index 0e584bd6..c08e91ed 100644 --- a/trento/xml/article_sap_trento.xml +++ b/trento/xml/article_sap_trento.xml @@ -186,7 +186,7 @@ As agreed on https://confluence.suse.com/x/DAEcN on our Trento doc kick off If you do not have a &k8s; enterprise solution and you would - like to test Trento, &suse; Rancher's K3s could be an easy + like to test &trentopremium;, &suse; Rancher's K3s could be an easy way to get started. But beware that K3s default installation process deploys a single node &k8s; cluster, which is not a recommended setup for a stable Trento production instance. From 2700e01c26ba44118b0987b239abf69cc062c7b3 Mon Sep 17 00:00:00 2001 From: Alberto Bravo Date: Wed, 9 Aug 2023 13:16:14 +0200 Subject: [PATCH 05/21] Update trento/xml/article_sap_trento.xml Co-authored-by: Tom Schraitle --- trento/xml/article_sap_trento.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/trento/xml/article_sap_trento.xml b/trento/xml/article_sap_trento.xml index c08e91ed..e855addd 100644 --- a/trento/xml/article_sap_trento.xml +++ b/trento/xml/article_sap_trento.xml @@ -187,7 +187,7 @@ As agreed on https://confluence.suse.com/x/DAEcN on our Trento doc kick off If you do not have a &k8s; enterprise solution and you would like to test &trentopremium;, &suse; Rancher's K3s could be an easy - way to get started. But beware that K3s default installation process + way to get started. Keep in mind that K3s default installation process deploys a single node &k8s; cluster, which is not a recommended setup for a stable Trento production instance. From ff524c7aaed76802e394837eb2aab0c1ed985def Mon Sep 17 00:00:00 2001 From: Alberto Bravo Date: Wed, 9 Aug 2023 13:16:23 +0200 Subject: [PATCH 06/21] Update trento/xml/article_sap_trento.xml Co-authored-by: Tom Schraitle --- trento/xml/article_sap_trento.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/trento/xml/article_sap_trento.xml b/trento/xml/article_sap_trento.xml index e855addd..40529e47 100644 --- a/trento/xml/article_sap_trento.xml +++ b/trento/xml/article_sap_trento.xml @@ -233,7 +233,7 @@ As agreed on https://confluence.suse.com/x/DAEcN on our Trento doc kick off any other CNCF-certified &k8s; running on x86_64 architecture - A proper, production ready installation of Trento Server requires &k8s; + A proper, production ready installation of &t.server; requires &k8s; knowledge. The Helm chart is meant to be used by customers lacking such knowledge or wanting a quick start, but it delivers a basic deployment of the &t.server; with all the components running on a single node of the cluster. From 2fa3f0e2b0b95cf39266349a713ddc93534e71d9 Mon Sep 17 00:00:00 2001 From: Alberto Bravo Date: Wed, 9 Aug 2023 13:17:00 +0200 Subject: [PATCH 07/21] Update trento/xml/article_sap_trento.xml Co-authored-by: Tom Schraitle --- trento/xml/article_sap_trento.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/trento/xml/article_sap_trento.xml b/trento/xml/article_sap_trento.xml index 40529e47..055251a6 100644 --- a/trento/xml/article_sap_trento.xml +++ b/trento/xml/article_sap_trento.xml @@ -235,7 +235,7 @@ As agreed on https://confluence.suse.com/x/DAEcN on our Trento doc kick off A proper, production ready installation of &t.server; requires &k8s; knowledge. The Helm chart is meant to be used by customers lacking such knowledge - or wanting a quick start, but it delivers a basic deployment of the &t.server; with all the components running + or who want to get started quickly. However, Helm chart delivers a basic deployment of the &t.server; with all the components running on a single node of the cluster.
From 19bd0c6aafc9620880c5984be7c338ae0fbaaaa3 Mon Sep 17 00:00:00 2001 From: Alberto Bravo Date: Wed, 9 Aug 2023 13:17:22 +0200 Subject: [PATCH 08/21] Update trento/xml/article_sap_trento.xml Co-authored-by: Tom Schraitle --- trento/xml/article_sap_trento.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/trento/xml/article_sap_trento.xml b/trento/xml/article_sap_trento.xml index 055251a6..c2c9d2af 100644 --- a/trento/xml/article_sap_trento.xml +++ b/trento/xml/article_sap_trento.xml @@ -251,7 +251,7 @@ As agreed on https://confluence.suse.com/x/DAEcN on our Trento doc kick off toms 2021-12-06: do we have UDP here too? - The web component of the &t.server; must be reachable via HTTP (port TCP/80) or via HTTPS (port TCP/443) if SSL is enabled, from any &t.agent; host. + From any &t.agent; host, the web component of the &t.server; must be reachable via HTTP (port TCP/80) or via HTTPS (port TCP/443) if SSL is enabled. From 3a9dd5286e84c71fea60f5613607e3d3fe88e7e8 Mon Sep 17 00:00:00 2001 From: Alberto Bravo Date: Wed, 9 Aug 2023 13:17:35 +0200 Subject: [PATCH 09/21] Update trento/xml/article_sap_trento.xml Co-authored-by: Tom Schraitle --- trento/xml/article_sap_trento.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/trento/xml/article_sap_trento.xml b/trento/xml/article_sap_trento.xml index c2c9d2af..b2abbd24 100644 --- a/trento/xml/article_sap_trento.xml +++ b/trento/xml/article_sap_trento.xml @@ -2097,7 +2097,7 @@ In the Trento dashboard, go to the overview corresponding to the object for whic - When updating from a Trento version lower than 2.0.0 to version 2.0.0 or higher, an additional parameter + When updating from a Trento version lower than 2.0.0 to version 2.0.0 or higher, an additional flag must be set in the Helm command. This is a workaround for an existing bug for which we are currently working on a fix: helm upgrade \ From b920afa0db0b7be08bbf25bb2d98bf7515ba473a Mon Sep 17 00:00:00 2001 From: Alberto Bravo Date: Wed, 9 Aug 2023 13:18:02 +0200 Subject: [PATCH 10/21] Update trento/xml/article_sap_trento.xml Co-authored-by: Tom Schraitle --- trento/xml/article_sap_trento.xml | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/trento/xml/article_sap_trento.xml b/trento/xml/article_sap_trento.xml index b2abbd24..8fbc3ef6 100644 --- a/trento/xml/article_sap_trento.xml +++ b/trento/xml/article_sap_trento.xml @@ -2098,8 +2098,7 @@ In the Trento dashboard, go to the overview corresponding to the object for whic When updating from a Trento version lower than 2.0.0 to version 2.0.0 or higher, an additional flag - must be set in the Helm command. This is a workaround for an existing bug for which we are currently working - on a fix: + must be set in the Helm command: helm upgrade \ --install trento-server oci://registry.suse.com/trento/trento-server \ --set trento-web.adminUser.password=ADMIN_PASSWORD \ From 04e166955bd40a153444bf74d8ae9e092b11be68 Mon Sep 17 00:00:00 2001 From: Alberto Bravo Date: Wed, 9 Aug 2023 13:18:14 +0200 Subject: [PATCH 11/21] Update trento/xml/article_sap_trento.xml Co-authored-by: Tom Schraitle --- trento/xml/article_sap_trento.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/trento/xml/article_sap_trento.xml b/trento/xml/article_sap_trento.xml index 8fbc3ef6..482e2a88 100644 --- a/trento/xml/article_sap_trento.xml +++ b/trento/xml/article_sap_trento.xml @@ -2106,7 +2106,7 @@ In the Trento dashboard, go to the overview corresponding to the object for whic - If email alerting has been enabled, then the corresponding trento-web.alerting parameters + If email alerting has been enabled, then the corresponding trento-web.alerting parameters should be set in the Helm command as well. From a55114a43822721b62a6ff09e918d98964ca661b Mon Sep 17 00:00:00 2001 From: Alberto Bravo Date: Wed, 9 Aug 2023 13:18:27 +0200 Subject: [PATCH 12/21] Update trento/xml/article_sap_trento.xml Co-authored-by: Tom Schraitle --- trento/xml/article_sap_trento.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/trento/xml/article_sap_trento.xml b/trento/xml/article_sap_trento.xml index 482e2a88..2d6d0422 100644 --- a/trento/xml/article_sap_trento.xml +++ b/trento/xml/article_sap_trento.xml @@ -2178,7 +2178,7 @@ In the Trento dashboard, go to the overview corresponding to the object for whic [...] - Check the version in the Hosts overview of the &t.web; (URL + Check the version in the Hosts overview of the &t.web; (URL http://TRENTO_SERVER_HOSTNAME). From cbf367b9c8b2edcfbe0f33a2f50f72b382e0e9c5 Mon Sep 17 00:00:00 2001 From: Alberto Bravo Date: Wed, 9 Aug 2023 13:18:41 +0200 Subject: [PATCH 13/21] Update trento/xml/article_sap_trento.xml Co-authored-by: Tom Schraitle --- trento/xml/article_sap_trento.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/trento/xml/article_sap_trento.xml b/trento/xml/article_sap_trento.xml index 2d6d0422..46ca2b4f 100644 --- a/trento/xml/article_sap_trento.xml +++ b/trento/xml/article_sap_trento.xml @@ -2191,7 +2191,7 @@ In the Trento dashboard, go to the overview corresponding to the object for whic
Uninstalling &t.server; If &t.server; was deployed manually, then you need to uninstall it manually. - If &t.server; was deployed using the helm chart, then w can use Helm to uninstall it as follows: + If &t.server; was deployed using the Helm chart, use Helm to uninstall it as follows: helm uninstall trento-server
From acc1952c5ef59b350e7db9a41101c10731e3fe47 Mon Sep 17 00:00:00 2001 From: Alberto Bravo Date: Thu, 10 Aug 2023 10:23:05 +0200 Subject: [PATCH 14/21] Update trento/xml/article_sap_trento.xml Co-authored-by: Tom Schraitle --- trento/xml/article_sap_trento.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/trento/xml/article_sap_trento.xml b/trento/xml/article_sap_trento.xml index 46ca2b4f..7352a8d1 100644 --- a/trento/xml/article_sap_trento.xml +++ b/trento/xml/article_sap_trento.xml @@ -256,7 +256,7 @@ As agreed on https://confluence.suse.com/x/DAEcN on our Trento doc kick off - The checks engine component of the &t.server;, called Wanda, must be reachable via Advanced Message Queuing Protocol or AMQP (port TCP/5672), from any &t.agent; host. + From any &t.agent; host, the checks engine component of the &t.server;, called Wanda, must be reachable via Advanced Message Queuing Protocol or AMQP (port TCP/5672). From 0ed965520ed5281c4bb1d477c5ef7469e2388171 Mon Sep 17 00:00:00 2001 From: Alberto Bravo Date: Thu, 10 Aug 2023 10:23:29 +0200 Subject: [PATCH 15/21] Update trento/xml/article_sap_trento.xml Co-authored-by: Tom Schraitle --- trento/xml/article_sap_trento.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/trento/xml/article_sap_trento.xml b/trento/xml/article_sap_trento.xml index 7352a8d1..c2a3e2de 100644 --- a/trento/xml/article_sap_trento.xml +++ b/trento/xml/article_sap_trento.xml @@ -320,8 +320,8 @@ As agreed on https://confluence.suse.com/x/DAEcN on our Trento doc kick off &t.server; consists of a few components which are delivered as container images and meant to be deployed on a &k8s; cluster. A manual deployment of these components in a production - ready fashion requires &k8s; knowledge. Customers lacking such knowledge or wanting a quick start - with Trento, can use the Trento helm chart, which automates the deployment of all the required components + ready fashion requires &k8s; knowledge. Customers lacking such knowledge or who want to get started quickly + with Trento, can use the Trento Helm chart. This approach automates the deployment of all the required components on a single &k8s; cluster node. You can use the Trento helm chart in order to install Trento Server on a existing &k8s; cluster as follows: From de6edbd30157921c3b1da8754dcf141dfc77182a Mon Sep 17 00:00:00 2001 From: Alberto Bravo Date: Thu, 10 Aug 2023 10:23:39 +0200 Subject: [PATCH 16/21] Update trento/xml/article_sap_trento.xml Co-authored-by: Tom Schraitle --- trento/xml/article_sap_trento.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/trento/xml/article_sap_trento.xml b/trento/xml/article_sap_trento.xml index c2a3e2de..9f716d4a 100644 --- a/trento/xml/article_sap_trento.xml +++ b/trento/xml/article_sap_trento.xml @@ -322,7 +322,7 @@ As agreed on https://confluence.suse.com/x/DAEcN on our Trento doc kick off to be deployed on a &k8s; cluster. A manual deployment of these components in a production ready fashion requires &k8s; knowledge. Customers lacking such knowledge or who want to get started quickly with Trento, can use the Trento Helm chart. This approach automates the deployment of all the required components - on a single &k8s; cluster node. You can use the Trento helm chart in order to install Trento Server + on a single &k8s; cluster node. You can use the Trento Helm chart in order to install &t.server; on a existing &k8s; cluster as follows: From 04f6a03f521e6a4be9adfa7885ef477cf391cbae Mon Sep 17 00:00:00 2001 From: Alberto Bravo Date: Thu, 10 Aug 2023 10:26:15 +0200 Subject: [PATCH 17/21] Update trento/xml/article_sap_trento.xml Co-authored-by: Tom Schraitle --- trento/xml/article_sap_trento.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/trento/xml/article_sap_trento.xml b/trento/xml/article_sap_trento.xml index 9f716d4a..205084ed 100644 --- a/trento/xml/article_sap_trento.xml +++ b/trento/xml/article_sap_trento.xml @@ -335,7 +335,7 @@ As agreed on https://confluence.suse.com/x/DAEcN on our Trento doc kick off - Install the &t.server; pulling the Trento helm chart with Helm: + Install the &t.server; by pulling the Trento Helm chart with Helm: helm upgrade \ --install trento-server oci://registry.suse.com/trento/trento-server \ From 370b2a6d0a76c48c3ee5a8465341f5045e97271b Mon Sep 17 00:00:00 2001 From: Alberto Bravo Date: Thu, 10 Aug 2023 10:30:15 +0200 Subject: [PATCH 18/21] Update trento/xml/article_sap_trento.xml Co-authored-by: Tom Schraitle --- trento/xml/article_sap_trento.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/trento/xml/article_sap_trento.xml b/trento/xml/article_sap_trento.xml index 205084ed..9e0da610 100644 --- a/trento/xml/article_sap_trento.xml +++ b/trento/xml/article_sap_trento.xml @@ -2082,7 +2082,7 @@ In the Trento dashboard, go to the overview corresponding to the object for whic -->
Updating &t.server; - The procedure to update &t.server; depends on how it was installed. + The procedure to update the &t.server; depends on how it was installed. If it was installed manually, then it must be updated manually using the latest versions of the container images available in SUSE public registry. If was installed using the Helm chart, it can be updated using the same Helm command as for the installation: From 21f87f4d636f52013c824dc84fd9dc200b6a6473 Mon Sep 17 00:00:00 2001 From: Alberto Bravo Date: Thu, 10 Aug 2023 10:30:59 +0200 Subject: [PATCH 19/21] Update trento/xml/article_sap_trento.xml Co-authored-by: Tom Schraitle --- trento/xml/article_sap_trento.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/trento/xml/article_sap_trento.xml b/trento/xml/article_sap_trento.xml index 9e0da610..354ab780 100644 --- a/trento/xml/article_sap_trento.xml +++ b/trento/xml/article_sap_trento.xml @@ -2084,7 +2084,7 @@ In the Trento dashboard, go to the overview corresponding to the object for whic Updating &t.server; The procedure to update the &t.server; depends on how it was installed. If it was installed manually, then it must be updated manually using the latest versions - of the container images available in SUSE public registry. If was installed using the + of the container images available in the SUSE public registry. If it was installed using Helm chart, it can be updated using the same Helm command as for the installation: helm upgrade \ --install trento-server oci://registry.suse.com/trento/trento-server \ From 6eee89b52cced2d8f3e7b0c8f1fa04a6bcead9f6 Mon Sep 17 00:00:00 2001 From: Alberto Bravo Date: Thu, 10 Aug 2023 10:34:48 +0200 Subject: [PATCH 20/21] Update trento/xml/article_sap_trento.xml Co-authored-by: Tom Schraitle --- trento/xml/article_sap_trento.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/trento/xml/article_sap_trento.xml b/trento/xml/article_sap_trento.xml index 354ab780..28e8d4b7 100644 --- a/trento/xml/article_sap_trento.xml +++ b/trento/xml/article_sap_trento.xml @@ -2093,7 +2093,7 @@ In the Trento dashboard, go to the overview corresponding to the object for whic A few things to consider: - Remember to add set the helm experimental flag if you are using a version of Helm lower than 3.8.0. + Remember to set the helm experimental flag if you are using a version of Helm lower than 3.8.0. From 5ca6d842a5da8951194874123d2a6668adcd2ff4 Mon Sep 17 00:00:00 2001 From: Alberto Bravo Date: Thu, 10 Aug 2023 10:35:50 +0200 Subject: [PATCH 21/21] Update trento/xml/article_sap_trento.xml Co-authored-by: Tom Schraitle --- trento/xml/article_sap_trento.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/trento/xml/article_sap_trento.xml b/trento/xml/article_sap_trento.xml index 28e8d4b7..70f444a7 100644 --- a/trento/xml/article_sap_trento.xml +++ b/trento/xml/article_sap_trento.xml @@ -417,7 +417,7 @@ As agreed on https://confluence.suse.com/x/DAEcN on our Trento doc kick off --set trento-web.adminUser.password=ADMIN_PASSWORD - Monitor the creation and start-up of the Trento Server pods and wait until they are all in ready/running status: + Monitor the creation and start-up of the &t.server; pods and wait until they are all ready and running: watch kubectl get pods